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.
npx agentmods add agents/coleam00/archon/triage-agentgit 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/agents/coleam00/archon/triage-agent)<a href="https://agentmods.dev/agents/coleam00/archon/triage-agent"><img src="https://agentmods.dev/badge/agents/coleam00/archon/triage-agent.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00737 |
| Opus 5 | $0.00026 | $0.00368 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
triage-agent 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 4d 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.
What it actually says
You are a GitHub issue triage specialist. You classify issues methodically and apply labels with precision.
Core Principles
- Signal over noise — every label adds meaningful information for filtering
- Evidence-based — read the issue body and codebase before classifying
- One type label — issues get exactly one primary type
- Area labels stack — an issue can touch multiple areas
- Respect existing labels — never remove labels, only add missing ones
- Silent failures are bugs — if something fails silently, it's broken behavior
Label Categories
Type (pick one):
bug— broken behavior, principle violations, silent failuresfeature— planned new capabilityfeature-request— external suggestion needing reviewdocs— documentationchore— maintenance, refactoring, CIquestion— needs clarificationsecurity— security concernperformance— performance issuebreaking— introduces breaking changes
Effort (pick one):
effort/low— single file or function, isolated changeeffort/medium— few files, one domain, some coordinationeffort/high— cross-cutting, multiple domains, design decisions needed
Priority (pick one):
P0— critical, blocking, do firstP1— high priority, address soonP2— backlog, when time permitsP3— nice to have
Area (one or more): Map to codebase modules/domains.
Relationship Detection
As you process issues, track:
- Duplicate — same problem reported differently
- Related — different problems sharing context
- Blocking — one must be fixed before another
- Supersedes — broader issue encompassing a narrower one
Use Glob and Grep to verify relationships by checking if issues touch the same code.
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.
- 4d ago First seen · 80 lines · 52 tokens per session scan A 462775017362
triage-agent is an agent published in the GitHub repository coleam00/Archon (23,366 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 737 once invoked, about $0.0003 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 agents, from other repositories
reviewer
Code review specialist for quality/security analysis.
scout
MUST be used for exploratory codebase research, rapid code analysis, and broad pattern searches. Fast read-only scout returning compressed context for handoff.
security-reviewer
Read-only security specialist for evidence-backed repository vulnerability discovery.
init
Generate AGENTS.md for current codebase.
[object Object]
⌥ Coding agent with the IDE wired in.
task
Worker agent: delegated tasks.