Archon is a workflow engine for AI coding agents that turns development processes into YAML-defined sequences with phases, validation gates, and artifacts. Developers use it to run repeatable processes such as planning, implementation, testing, code review, and pull-request creation across projects. The catalogue entries provide commands, agents, skills, hooks, instructions, and settings for working with Archon.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/coleam00/ArchonWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/coleam00/archon/maintainer-review-docs-impact)<a href="https://agentmods.dev/commands/coleam00/archon/maintainer-review-docs-impact"><img src="https://agentmods.dev/badge/commands/coleam00/archon/maintainer-review-docs-impact/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/coleam00/archon/maintainer-review-docs-impact"><img src="https://agentmods.dev/badge/commands/coleam00/archon/maintainer-review-docs-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.01010 |
| Opus 5 | $0.00015 | $0.00505 |
| Sonnet 5 | $0.00006 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
maintainer-review-docs-impact scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer Review — Docs Impact
You are a docs-impact reviewer. Run only when the diff adds, removes, or renames public APIs, CLI flags, environment variables, or other user-facing behavior. Your job: catch missing or stale documentation.
Workflow ID: $WORKFLOW_ID
Phase 1: LOAD
PR_NUMBER=$(cat $ARTIFACTS_DIR/.pr-number)
gh pr diff $PR_NUMBER
Find docs locations:
ls packages/docs-web/src/content/docs/ 2>/dev/null
ls docs/ 2>/dev/null
ls README.md CONTRIBUTING.md CLAUDE.md 2>/dev/null
The project's docs site is at packages/docs-web/ (Starlight). User-facing docs published to archon.diy. Repo-level docs include CLAUDE.md, CONTRIBUTING.md, and any docs/ content.
Phase 2: ANALYZE
For each user-facing change in the diff, identify the docs that should be updated:
What counts as user-facing
- New CLI command or flag (in
packages/cli/). - New environment variable.
- New / removed / renamed API route (in
packages/server/src/routes/). - New workflow node type, command file, or workflow YAML field.
- New configuration field in
.archon/config.yaml. - Change in default behavior that an existing user would notice.
What doesn't
- Internal refactors with no API change.
- Test-only changes.
- Bug fixes that restore documented behavior.
For each user-facing change
- New surface: is there a docs page describing it? Is it linked from a landing page or the relevant section?
- Changed surface: are existing docs pages still accurate? Do they need updates?
- Removed surface: are existing references stale?
grepthe docs site for old name.
Specific places to check
packages/docs-web/src/content/docs/getting-started/— quickstart, install, concepts.packages/docs-web/src/content/docs/guides/— workflow authoring, hooks, MCP, scripts.packages/docs-web/src/content/docs/reference/— CLI, variables, configuration.packages/docs-web/src/content/docs/adapters/— Slack, Telegram, GitHub, Discord, Web.packages/docs-web/src/content/docs/deployment/— Docker, cloud.CLAUDE.md— only if the change affects how agents working in this repo should behave.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 119 lines · 29 tokens per session scan A a8388f147db1
maintainer-review-docs-impact is a command published in the GitHub repository coleam00/Archon (23,407 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,010 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
cleanup
Autonomous cleanup-loop iteration: discover ONE target → complete execution → verify → report. Runs stateless: derive from current tree; assume prior runs left it consistent.
review
Run code review on files or recent changes.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.