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.
Borrowing it
Nothing to install: this file belongs to coleam00/Archon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/coleam00/Archon/dev/.claude/commands/github_bug_fix/implement-fix.mdgit 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/implement-fix)<a href="https://agentmods.dev/commands/coleam00/archon/implement-fix"><img src="https://agentmods.dev/badge/commands/coleam00/archon/implement-fix/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/implement-fix"><img src="https://agentmods.dev/badge/commands/coleam00/archon/implement-fix.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.00009 | $0.00878 |
| Opus 5.5 | $0.00004 | $0.00351 |
| Sonnet 5.5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
implement-fix 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Fix: GitHub Issue #$ARGUMENTS
Prerequisites
- RCA document exists at
.agents/rca/issue-$ARGUMENTS.md - If not, run
/rca $ARGUMENTSfirst
RCA Document to Reference
Read RCA: .agents/rca/issue-$ARGUMENTS.md
Optional — View GitHub issue for latest context:
gh issue view $ARGUMENTS
Implementation Instructions
1. Read and Understand RCA
- Read the ENTIRE RCA document thoroughly
- Understand the root cause
- Review the proposed fix strategy
- Note all files to modify
- Review testing requirements
2. Verify Current State
Before making changes:
- Confirm the issue still exists in current code
- Check current state of affected files
- Review any recent changes to those files since RCA was written
3. Implement the Fix
Following the "Proposed Fix" section of the RCA:
For each file to modify:
a. Read the existing file
- Understand current implementation
- Locate the specific code mentioned in RCA
b. Make the fix
- Implement the change as described
- Follow the fix strategy exactly
- Maintain Archon coding conventions (see AGENTS.md)
- Respect package boundaries
- Use proper import patterns (
import typefor type-only)
c. Handle related changes
- Update related code affected by the fix
- Ensure consistency across packages
- Update imports if needed
4. Add/Update Tests
Following the "Testing Requirements" from RCA:
Important Archon test patterns:
- Use
spyOn()for internal module mocking (notmock.module()unless absolutely necessary) - If adding
mock.module(), check if the test file needs its own batch in package.json - Place tests alongside source files or in existing test directories
- Follow existing test patterns in the affected package
5. Check Your Changes
Run the tests that cover what you changed, and lint and type-check the packages you touched. CI is the full validation; don't run bun run validate.
If a check fails because of your change:
- Fix it
- Re-run that check
- Don't proceed until it passes
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 Changed · -5 lines cbbde26579f2
- 17d ago Changed 7176d6685af2
- 1mo ago First seen · 154 lines · 9 tokens per session scan A 4529edd0e008
implement-fix is a command published in the GitHub repository coleam00/Archon (23,752 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 878 once invoked, about $0.0000 per session on Opus 5.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
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-codebase-map
Reverse-engineer a brownfield codebase into current-state module boundaries, integration-point inventory, tech-debt register, and dependency graph via static analysis.