AgentSys
A gated, resumable delivery system for turning development tasks into reviewed and merged changes.
- Source repo
- agent-sh/agentsys
- Stars
- ★ 1k
- Last updated
- 4d ago
- License
- MIT
- Primary language
- JavaScript
- FA score
- 52/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Cost
- Free software; you pay for model usage
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A GitHub-based engineering team that wants a selected issue to move through planning approval, implementation, review, and merge in one workflow.
- Not a fit if
- Teams that don't want automated commits, pushes, PRs, and merges to remote repos
- Users without Git or Node.js 18+ available
- Source review
- 52/100 · Major gaps
What does this agent do, and when should you use it?
AgentSys is a modular runtime for orchestrating software-development agents and a marketplace/installer for plugins under agent-sh. It combines 24 plugins, 49 agents, and 44 skills behind slash commands for task discovery, implementation, review, documentation sync, release, and merge workflows. Its documented pipelines use phase gates and persistent state, and /next-task creates isolated worktrees for task execution. The system is documented for Claude Code, Codex CLI, OpenCode, Cursor, and Kiro, with an npm-based installer. It fits teams that want repeatable engineering delivery workflows, provided they are comfortable with CLI, Git, and platform-specific workflow dependencies.
With /next-task, AgentSys selects work from GitHub Issues, GitHub Projects, GitLab, or a local file; creates a worktree; explores the repository; prepares a plan for user approval; implements it; runs deslop and test-coverage checks; iterates through review; validates delivery; syncs documentation; and invokes /ship for PR creation, CI monitoring, and merge. /prepare-delivery runs pre-review gates, conditional config linting, a review loop, delivery validation, and docs sync without pushing or opening a PR, while /gate-and-ship composes it with /ship. /repo-intel uses agent-analyzer to collect Git-history intelligence, AST symbols, and project metadata into platform-state caches; /drift-detect gathers issues, documentation, and code exports with JavaScript collectors before semantic analysis. Other documented commands include /audit-project, /perf, /sync-docs, /agnix, /onboard, /consult, and /release.
- A GitHub-based engineering team that wants a selected issue to move through planning approval, implementation, review, and merge in one workflow.
- A developer with finished local changes who wants
/prepare-deliveryto run cleanup, coverage checks, multi-role review, validation, and documentation sync before deciding whether to open a PR. - A repository maintainer who needs
/shipto detect CI and deployment tooling, push a branch, create a PR, follow CI, address review comments, and merge. - A contributor joining a JavaScript, Rust, Go, Python, C/C++, Java, or Deno project who needs
/onboardto summarize its stack, key files, and conventions. - A team maintaining skills, agent prompts, hooks, and tool configuration that wants
/agnixvalidation for structure, security, consistency, and cross-platform configuration rules. - A project owner who suspects issues, plans, or documentation examples have diverged from implementation and needs
/drift-detector/sync-docs.
How do you install or deploy this agent?
Git and Node.js 18+ are required. Install the cross-platform npm installer with npm install -g agentsys && agentsys. For Codex CLI, run agentsys --tool codex; for Claude Code, run agentsys --tool claude. Claude Code can also use /plugin marketplace add agent-sh/agentsys, followed by a plugin install such as /plugin install next-task@agentsys. GitHub workflows require an authenticated gh; GitLab workflows require an authenticated glab. /agnix additionally requires the separately installed agnix CLI.
How do you use this agent?
After installation, run /onboard for an overview of the current repository. Run /next-task for the full task-to-production workflow; it requests plan approval before implementation. Run /prepare-delivery for quality gates without creating a PR, then /ship for commit, PR, CI, and merge handling, or use /gate-and-ship to chain both. Resume an interrupted task workflow with /next-task --resume. Initialize repository intelligence with /repo-intel init, then query it with /repo-intel query hotspots.
What are this agent's strengths and limitations?
- Composes task discovery, isolated worktrees, plan approval, implementation, review, validation, documentation sync, and PR merge into standalone or chained commands.
- Uses specialized responsibilities, phase gates, and persistent state for long-running delivery workflows that can be resumed.
/repo-intelcentralizes cached Git history, AST symbols, and project metadata for reuse by multiple plugins./agnixdocuments 423 validation rules and SARIF output, enabling agent-configuration checks in GitHub Code Scanning.- Provides documented installation paths for Claude Code, Codex CLI, OpenCode, Cursor, and Kiro.
- It requires Git and Node.js 18+, while GitHub and GitLab delivery workflows also depend on authenticated
ghorglabclients. /shipis designed to commit, push, create PRs, monitor CI, address comments, merge, and clean up; that scope may not fit teams that do not want automated remote repository changes./prepare-deliveryis the documented non-shipping alternative.- Some functions have added tooling dependencies:
/agnixneeds the agnix CLI, and/repo-intelrelies on agent-analyzer installed through npm. - The reported benchmarks are tied to named tasks, repository, and model configurations, so they do not establish equivalent cost or quality outcomes for every project or model.
How does this agent compare with similar options?
The README compares its structured pipeline with direct model use without AgentSys. For the documented documentation-improvement task, it reports Sonnet + AgentSys as comparable in result quality to Opus + AgentSys, while raw Opus produced more generic, less project-specific output. /drift-detect is also explicitly positioned against multi-agent collection: it uses JavaScript collectors plus one semantic analysis call and reports a 77% token reduction versus multi-agent approaches.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| AgentSys This agent | 52 · Major gaps | CLIFree + model costs | ★ 1k | 4d ago | JavaScript | Codex · Claude Code |
| Agent Orchestrator | 48 · Major gaps | Desktop appFree + model costs | ★ 14k | today | Go | Codex · Claude Code |
| Argot Repository Style Analyzer | 93 · Excellent | CLIFree | ★ 52 | 2mo ago | Rust | Claude Code |
| Jev Review | 81 · Good | Agent plugin / skillFree + model costs | ★ 247 | 1mo ago | TypeScript | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows basic security measures: SECURITY.md mentions command injection prevention, path traversal prevention, and input validation, but no implementation details. User confirmation: /next-task includes user approval step, /ship has --dry-run, but other commands like /deslop apply may modify files directly. Data flow transparency limited, no detailed explanation of data collection and transmission. Sensitive data handling: SECURITY.md reminds users not to commit secrets, but no system-level handling. Dependency security: 6.0.1 removed vulnerable js-yaml, but no full audit. External effects: /ship and /next-task commit, push, merge PRs, affecting external systems, but provide --dry-run. Rollback: no explicit rollback mechanism, but /next-task has --abort. Source attribution: plugins from agent-sh org, but publisher unverified.
Self-consistency: README claims 24 plugins, 49 agents, 44 skills, consistent with description, but not verified against actual files. Dependency availability: depends on external tools like agnix CLI, gh CLI, but no handling for missing tools. Failure messages: no specific error handling docs, but tests cover some edge cases.
Audience clear as developers, scenarios cover code development, review, release. Capability boundaries: each agent has single responsibility, but no explicit limits. Trigger precision: commands have clear parameters, but no trigger condition details. Environment fit: supports multiple platforms, but no detailed configuration guide.
Information architecture clear, README has TOC and command list. Install notes provide npm installation. Naming stable, command and agent names consistent. Examples and FAQ: README provides command examples, but no FAQ. Known limitations: SECURITY.md mentions no security guarantee, but no specific limitations. License MIT, version 6.0.1, CHANGELOG exists but not provided. Maintenance responsibility: author Avi Fenesh, but no maintenance plan.
Output usability: command outputs have clear formats, e.g., /deslop report. Marginal value: provides various automation commands, saving time. Cost benefit: README provides benchmarks showing Sonnet + agentsys cheaper and comparable quality to raw Opus.
Claim traceability: README claims 3518 tests, but no test results provided. Cross-source corroboration: no external verification. Fact/inference separation: README distinguishes benchmarks and inferences, but not explicitly labeled.
- Publisher identity unverified, use with caution.
- Agents can perform modifying operations (e.g., /ship, /deslop apply), always review changes before running.
- Depends on external tools (e.g., agnix CLI), ensure they are installed.
- Security measures are limited, no implementation details provided.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
Changed - AGENTS.md says every change reaches main through a PR, with no exception for small fixes or hotfixes, and drops the 30-minute wait on Copilot, Claude, Gemini and Codex reviews. A PR gets a self-review (a fresh-context subagent reviews the diff and posts it as a PR comment), revuto and CI comments and failures are addressed, and when revuto is capped or down the self-review is enough and the PR body says so. agent-docs/release.md, checklists/release.md and the bump-version next steps merge the release commit through a PR and push only the tag, not main or --tags (#423 …View on GitHub ↗ -
Release notes excerpt
Changed - The claude.yml and claude-code-review.yml workflows run claude-code-action v1.0.232 with claude_args: --model claude-opus-5-5. The old model: input is not an input of the action at v1.0.70 or later, so the claude-opus-4-5-20251101 pin never took effect. - The README consult table names the current model families: Claude claude-haiku-4-5 / claude-sonnet-5 / claude-opus-5-5 (plus claude-fable-5-1 for explicit --model), Codex gpt-6-sol for low and medium effort and gpt-6-astra for high and max. …View on GitHub ↗ -
Release notes excerpt
Added - CI runs the jest suite on windows-latest as well as Linux, with fail-fast disabled so a Windows-only failure does not hide the Linux result (#392). The Windows-specific paths in this repo - where.exe executable resolution, PATHEXT-aware lookups, and the cmd.exe routing .cmd shims have needed since the CVE-2024-27980 fix - had never been exercised by CI: every regression in them so far was found by a user on Windows or by reading the code, which is why one defect class took three PRs to close. …View on GitHub ↗
FAQ
Is AgentSys limited to Claude Code?
Is there a human checkpoint before implementation?
/next-task documents user plan approval before implementation. /prepare-delivery can also be run independently and does not push or create PRs.Which commands can change a remote repository?
/ship can commit, push, create a PR, wait for CI, address review comments, merge, and clean up. GitHub and GitLab workflows require their authenticated CLIs.Does configuration linting need extra setup?
/agnix command requires the separately installed agnix CLI, available through npm, Cargo, or Homebrew.