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/validation/validate-2.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/validate-2)<a href="https://agentmods.dev/commands/coleam00/archon/validate-2"><img src="https://agentmods.dev/badge/commands/coleam00/archon/validate-2/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/validate-2"><img src="https://agentmods.dev/badge/commands/coleam00/archon/validate-2.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.09818 |
| Opus 5.5 | $0.00000 | $0.03927 |
| Sonnet 5.5 | $0.00000 | $0.01964 |
| Haiku 4.5 | $0.00000 | $0.00982 |
Grade C, and why
validate-2 scanned grade C with 2 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "${WORK_DIR}"/remote-coding-test-* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3090/health | jq How it starts
The opening of the file, as written. The whole thing — 1,153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultimate Validation Command (Updated January 2026)
Run comprehensive end-to-end validation of the Remote Agentic Coding Platform including Docker, Test Adapter, Database, and full GitHub workflow execution.
The key test (Phase 8): Creates a GitHub issue, then invokes the full workflow via issue comments:
@Archon /command-invoke prime- Analyze codebase@Archon /command-invoke plan-feature- Create implementation plan@Archon /command-invoke execute- Implement changes and create PR- (Phase 9)
@Archon /command-invoke review-pr- Review the created PR
Usage:
/validation:validate-2 <ngrok-url>
Example:
/validation:validate-2 https://trinity-nonadverbial-enharmonically.ngrok-free.dev
Prerequisites:
- ngrok running and exposing port 3090 (for GitHub webhooks)
.envfile configured with all required credentials- GitHub CLI (
gh) authenticated - Docker installed and running
Updated for:
- Bun runtime (not npm)
- Archon paths (
~/.archon/workspaces/owner/repo) - 6 database tables (codebases, conversations, sessions, command_templates, isolation_environments, workflow_runs)
- Worktree isolation with database tracking
- Full GitHub workflow: Issue → Prime → Plan → Execute → PR → Review
- Comprehensive command testing (/help, /clone, /repos, /templates, /status, /getcwd, /setcwd, /init, /reset, /worktree cleanup, /worktree orphans)
- PR/Issue worktree sharing verification
- GitHub close event cleanup trigger
- Database consistency checks (orphaned records)
Phase 1: Foundation Validation
1.1 Type Checking
bun run type-check
Expected: Zero TypeScript errors
1.2 Linting
bun run lint
Expected: Zero lint diagnostics (warnings fail too)
1.3 Code Formatting
bun run format:check
Expected: All files included by the formatter configuration in biome.jsonc pass Biome checks
1.4 Unit Tests
bun test
Expected: All critical tests pass
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.
- 6d ago Changed 9217145c489d
- 9d ago Changed 44807e796f1d
- 1mo ago First seen · 1,153 lines · 0 tokens per session scan C 981df53026f5
validate-2 is a command published in the GitHub repository coleam00/Archon (23,752 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,818 tokens. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
e2e
Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.
test-coverage
Analyze test coverage and generate missing tests.
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.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
qawolfCliRunResults.template
How to use what qawolf run get --run-id --json returns, and how to read the Playwright trace it links to.