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 commands/coleam00/archon/code-reviewgit clone --depth 1 https://github.com/coleam00/ArchonWhat 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.00014 | $0.00780 |
| Opus 5 | $0.00007 | $0.00390 |
| Sonnet 5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
code-review 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 2d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review: Pre-Commit Quality Check
Objective
Perform a thorough technical code review on recently changed files, checking for bugs, security issues, and adherence to Archon's documented conventions.
Process
1. Gather Codebase Context
Read the project conventions to understand what standards to enforce:
- Read
CLAUDE.mdfor project-wide conventions - Read any relevant
.claude/rules/files for domain-specific patterns
2. Identify Changes to Review
git status
git diff HEAD
git diff --stat HEAD
Check for new untracked files:
git ls-files --others --exclude-standard
Read each new file in its entirety. Read each changed file in its entirety (not just the diff) to understand full context.
3. Review Checklist
For each changed or new file, analyze for:
Logic Errors
- Off-by-one errors, incorrect conditionals
- Missing error handling or silent failures
- Race conditions (especially in async/streaming code)
- Incorrect TypeScript type narrowing
Security Issues
- SQL injection in raw queries
- XSS in rendered content
- Exposed secrets or API keys
- Insecure data handling
Performance Problems
- N+1 database queries
- Missing cleanup (event listeners, intervals, AbortControllers)
- Unnecessary re-renders in React components
- Unbounded array growth
Type Safety
- Use of
anywithout justification - Missing type annotations on functions
- Incorrect type assertions (
ascasts) - Overly broad types where narrow types exist
Archon-Specific Conventions
- Import patterns:
import typefor type-only imports, noimport * as core - Use
execFileAsyncnotexecfor git operations - Never
git clean -fd - Structured Pino logging with
{domain}.{action}_{state}event naming bun run testnotbun testfrom repo rootmock.module()isolation (separate test batches for conflicting mocks)- ESLint zero-warnings policy
Package Boundary Compliance
- No circular dependencies between packages
@archon/gitand@archon/pathsmust not import from@archon/core@archon/workflowsinjects deps via narrow interfaces, not direct core imports
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.
- 2d ago First seen · 114 lines · 14 tokens per session scan A dd1b5ea3c6b8
code-review is a command published in the GitHub repository coleam00/Archon (23,339 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 780 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
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
triage
Classify/label newly opened GitHub issues missing labels.
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
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.
hello
Say hello.