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/execution-reportgit 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.00007 | $0.00476 |
| Opus 5 | $0.00003 | $0.00238 |
| Sonnet 5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
execution-report 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Report
Review and deeply analyze the implementation you just completed.
Context
You have just finished implementing a feature or fix. Before moving on, reflect on:
- What you implemented
- How it aligns with the plan
- What challenges you encountered
- What diverged and why
Generate Report
Save to: .agents/execution-reports/[feature-name].md
Meta Information
- Plan file: [path to plan that guided this implementation]
- Feature: [brief description]
- Files added: [list with full paths]
- Files modified: [list with full paths]
- Lines changed: +X -Y
Validation Results
Type Checking: ✅/❌ [details if failed]
Linting: ✅/❌ [details if failed]
Formatting: ✅/❌ [details if failed]
Tests: ✅/❌ [X passed, Y failed]
Full Validate: ✅/❌ [bun run validate result]
What Went Well
List specific things that worked smoothly:
- [concrete examples from this implementation]
Challenges Encountered
List specific difficulties:
- [what was difficult and why, with file:line references]
Divergences from Plan
For each divergence, document:
[Divergence Title]
- Planned: [what the plan specified]
- Actual: [what was implemented instead]
- Reason: [why this divergence occurred]
- Type: [Better approach found | Plan assumption wrong | Security concern | Performance issue | Package boundary constraint | Other]
Skipped Items
List anything from the plan that was not implemented:
- [what was skipped]
- Reason: [why it was skipped]
Archon-Specific Observations
- Package boundaries respected: [yes/no — any cross-package concerns?]
- Mock isolation: [any new mock.module() calls? Do they need separate test batches?]
- Import patterns: [any tricky import situations?]
Recommendations
Based on this implementation, what should change for next time?
- Plan command improvements: [suggestions]
- Execute command improvements: [suggestions]
- CLAUDE.md additions: [suggestions]
.claude/rules/updates: [suggestions]
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 · 79 lines · 7 tokens per session scan A 9baf9410ac82
execution-report is a command published in the GitHub repository coleam00/Archon (23,339 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 476 once invoked, about $0.0000 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.