D
Drix10/agent-flow
Guardrails for AI coding agents: run Claude Code, Codex, Gemini CLI, Cursor or Copilot unattended and come…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"drix10-agent-flow": {
"command": "npx",
"args": ["@drix10/agent-flow"]
}
}
}Parsed from the README we fetched on 2026-11-09; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"drix10-agent-flow": {
"command": "npx",
"args": ["@drix10/agent-flow"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio drix10-agent-flow -- npx @drix10/agent-flow
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 12 ★ · Drix10/agent-flow · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-10 · last seen 2026-11-14 · seen 5× · listed by 1 sources
- Score
- score 103 · 12 ★ · 1 sources · repo
- Install
npx @drix10/agent-flow
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx @drix10/agent-flow. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Drix10/agent-flow；first catalogued 2026-11-10；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.Leave your coding agent alone with your repo. Come back to a reviewed pull reque
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
One agent builds. A second reviews. A third tests. A guard keeps all three out of what they must never touch.
Install · What you come back to · How it works · Harnesses · FAQ
## Install
bash
npx @drix10/agent-flow install --harness claude
Then tell your agent "use the agent-flow-bootstrap skill": it reads the repo and asks what must never be touched. After that, hand it a task:
bash
npx @drix10/agent-flow run "Add a --json flag so CI can parse the output"
That's all of it. It runs in its own git worktree and stops with checked work and a draft pull request waiting for you. Works with Claude Code, Codex, Gemini CLI, Cursor, Copilot, Windsurf, Pi and anything that reads AGENTS.md: swap claude for codex, gemini, cursor, copilot, windsurf or agents. Node.js 20+, no runtime dependencies, no package.json needed in your repo.
The guard blocks tool calls directly on Claude Code and Pi. On the other hosts the skills guide the agent and a pre-commit hook and CI catch the slips: what each host enforces.
## What you come back to
Real output from a run on a real repository (trimmed):
text
$ agent-flow status
Protection
✓ Claude Code guard hook is active
✓ 11 protected paths, 7 critical areas
✓ 1 review-only path: agents may add lines (a new CI test), a person reviews the pull request
Work
· #100000 is ready: reviewed, checked, not pushed
→ agent-flow run 100000 --pr to open the pull request
## Without it, and with it
| | ❌ Without Agent Flow | ✅ With Agent Flow |
| Who checks the work | The agent that wrote it | A second agent reviews, a third runs the checks |
| The new test isn't in the CI list | It edits the workflow or loosens the check to get green | It adds one line; every other CI change is refused |
| Push to main, force-push, --no-verify | Nothing stops it | Refused by the guard (Claude Code, Pi) or caught by the pre-commit hook |
| A check fails | You find out when you're back | It goes back to the Implementer, up to a round cap |
| When you're back | A whole diff to read | A draft pull request and a short list of what needs you |
| Docs and context | AGENTS.md describes the old behaviour | agent-flow doctor flags it |
| What happened | Ask the agent | A hash-chained audit log |
## From one real repo
Agent Flow ran for five days on a real C++ and Python research repository (294 role runs, about $83). The audit log recorded:
150 tool calls blocked, among them 20 reads of secret files, 2 pushes to main and 1 --no-verify. Not every block was right: 16 were false alarms from a Windows path bug, fixed in 1.2.6.
15 lines added to the CI workflow, none changed or deleted.
A median finished issue cost $0.90 and took 17 minutes, over 63 issues.
One repository, one maintainer: an example, not a benchmark.
More ways to install and run
Try it first, nothing installed and nothing written:
bash
npx @drix10/agent-flow scan
A read-only X-ray of any repository: languages, test and lint commands, CI, secret suspects. Or take just the skills, with any agent, via skills.sh (they call the CLI through npx, so there is still nothing to set up):
bash
npx skills add Drix10/agent-flow
Install the harness files, then ask your coding agent to bootstrap the repository:
Install · What you come back to · How it works · Harnesses · FAQ
## Install
bash
npx @drix10/agent-flow install --harness claude
Then tell your agent "use the agent-flow-bootstrap skill": it reads the repo and asks what must never be touched. After that, hand it a task:
bash
npx @drix10/agent-flow run "Add a --json flag so CI can parse the output"
That's all of it. It runs in its own git worktree and stops with checked work and a draft pull request waiting for you. Works with Claude Code, Codex, Gemini CLI, Cursor, Copilot, Windsurf, Pi and anything that reads AGENTS.md: swap claude for codex, gemini, cursor, copilot, windsurf or agents. Node.js 20+, no runtime dependencies, no package.json needed in your repo.
The guard blocks tool calls directly on Claude Code and Pi. On the other hosts the skills guide the agent and a pre-commit hook and CI catch the slips: what each host enforces.
## What you come back to
Real output from a run on a real repository (trimmed):
text
$ agent-flow status
Protection
✓ Claude Code guard hook is active
✓ 11 protected paths, 7 critical areas
✓ 1 review-only path: agents may add lines (a new CI test), a person reviews the pull request
Work
· #100000 is ready: reviewed, checked, not pushed
→ agent-flow run 100000 --pr to open the pull request
## Without it, and with it
| | ❌ Without Agent Flow | ✅ With Agent Flow |
| Who checks the work | The agent that wrote it | A second agent reviews, a third runs the checks |
| The new test isn't in the CI list | It edits the workflow or loosens the check to get green | It adds one line; every other CI change is refused |
| Push to main, force-push, --no-verify | Nothing stops it | Refused by the guard (Claude Code, Pi) or caught by the pre-commit hook |
| A check fails | You find out when you're back | It goes back to the Implementer, up to a round cap |
| When you're back | A whole diff to read | A draft pull request and a short list of what needs you |
| Docs and context | AGENTS.md describes the old behaviour | agent-flow doctor flags it |
| What happened | Ask the agent | A hash-chained audit log |
## From one real repo
Agent Flow ran for five days on a real C++ and Python research repository (294 role runs, about $83). The audit log recorded:
150 tool calls blocked, among them 20 reads of secret files, 2 pushes to main and 1 --no-verify. Not every block was right: 16 were false alarms from a Windows path bug, fixed in 1.2.6.
15 lines added to the CI workflow, none changed or deleted.
A median finished issue cost $0.90 and took 17 minutes, over 63 issues.
One repository, one maintainer: an example, not a benchmark.
More ways to install and run
Try it first, nothing installed and nothing written:
bash
npx @drix10/agent-flow scan
A read-only X-ray of any repository: languages, test and lint commands, CI, secret suspects. Or take just the skills, with any agent, via skills.sh (they call the CLI through npx, so there is still nothing to set up):
bash
npx skills add Drix10/agent-flow
Install the harness files, then ask your coding agent to bootstrap the repository:
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/drix10-agent-flow/)
- Source
- github · https://github.com/Drix10/agent-flow
- Browse by field
- Agent skills
- Traction
- 12 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.