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/route)<a href="https://agentmods.dev/commands/coleam00/archon/route"><img src="https://agentmods.dev/badge/commands/coleam00/archon/route/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/route"><img src="https://agentmods.dev/badge/commands/coleam00/archon/route.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.00000 | $0.01180 |
| Opus 5.5 | $0.00000 | $0.00472 |
| Sonnet 5.5 | $0.00000 | $0.00236 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
route 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 today.
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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Route One Build Item
Decide whether the build queue launches its next run on this item, and write the brief the run starts from. Triage already decided the route; you keep it thin. The next node performs what you declare: it launches archon-ship with your brief, or raises your attention item. You write nothing to the tracker, the repository or the state store yourself, and the checkout must be exactly as you found it when you finish.
The item: $INPUTS.url. Its issue, title and body, is in $ARTIFACTS_DIR/build/issue.md; read the body from there, because it is the text this decision is about. You may read the issue's comments and linked items with the tracker's CLI.
Read first
- The item's work item:
$INPUTS.record. It holds triage's verdict and five fields underfacts.triage, and underfacts.buildevery round the queue ran on it and every decision it made, with any maintainer's answer. Null means no queue has recorded it. - The brief the last decision left for this launch:
$INPUTS.brief. Empty means the item has not been launched yet, or a re-triage started it over. - The SDLC policy files this decision names, at
.archon/sdlc/policy/, falling back to the pack's defaults. This decision namesbuild.mdandrulings.md; the pack's defaults are in$INPUTS.policy_defaults. A project's file replaces the default whole: when it exists, do not read the default. - The project's direction document, where it has one, only when whether the item is in scope depends on it.
- The item's pull request as the forge reports it now:
$INPUTS.pull_request. It is the latest round's that recorded one, or the one triage routed it to continue; null means no round recorded one and triage named none. An open one whose head is in the item's repository is continued: the round finishes it and pushes onto its head, so the same pull request updates. Ask when it is closed or merged, or its head lives in another repository, unless a dated scope section or a maintainer's recorded answer already rules on it.
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.
- today First seen · 44 lines · 0 tokens per session scan A f5295f4a4ddc
route is a command published in the GitHub repository coleam00/Archon (23,701 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,180 tokens. 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-10-17.
Other commands, from other repositories
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
triage
Classify/label newly opened GitHub issues missing labels.
release
Release all packages at specified version.
cleanup
Autonomous cleanup-loop iteration: discover ONE target → complete execution → verify → report. Runs stateless: derive from current tree; assume prior runs left it consistent.
hatch3r-board-fill
Create epics and issues/work items from todo.md, reorganize the board with dependency analysis, readiness assessment, and implementation ordering. Supports GitHub, Azure DevOps, and GitLab.