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/frenzymath/archon/reviewgit clone --depth 1 https://github.com/frenzymath/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/frenzymath/archon/review)<a href="https://agentmods.dev/commands/frenzymath/archon/review"><img src="https://agentmods.dev/badge/commands/frenzymath/archon/review.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.00009 | $0.02843 |
| Opus 5 | $0.00005 | $0.01422 |
| Sonnet 5 | $0.00002 | $0.00569 |
| Haiku 4.5 | $0.00001 | $0.00284 |
Grade A, and why
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 5d 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lean4 Review
Read-only review of Lean proofs for quality, style, and optimization opportunities.
Non-destructive: Files are restored after analysis.
Usage
/lean4:review # Review changed files (default)
/lean4:review File.lean # Review specific file
/lean4:review File.lean --line=89 # Review single sorry
/lean4:review File.lean --line=89 --scope=deps # Review sorry + its dependencies
/lean4:review --scope=project # Review entire project (prompts)
Inputs
| Arg | Required | Description |
|---|---|---|
| target | No | File or directory to review |
| --scope | No | sorry, deps, file, changed, or project |
| --line | No | Line number for single-sorry scope |
| --codex | No | External review via Codex (interactive handoff) |
| --llm | No | Use llm CLI with model |
| --hook | No | Run custom analysis script |
| --json | No | Output structured JSON for external tools |
| --mode | No | batch (default) or stuck (triage) |
Scope Behavior
Scope levels:
| Scope | Description |
|---|---|
sorry |
Single sorry at --line (requires target file + --line) |
deps |
Sorry + same-file helpers and directly referenced lemmas (requires target file + --line) |
file |
All sorries in target file |
changed |
Files modified since last commit (git diff) |
project |
Entire project (requires confirmation) |
Defaults:
- No args →
--scope=changed - Target file provided →
--scope=file - Target +
--line→--scope=sorry - Triggered by prove/autoprove → matches current focus (
sorryorfile)
Note: Scope filtering is implemented by the reviewing agent, not the underlying scripts. The agent reads script output and filters results to match the requested scope.
Project-wide confirmation:
⚠️ This will review the entire project.
Proceed? (yes / no)
Output header always shows scope:
## Lean4 Review Report
**Scope:** Core.lean:89 (single sorry)
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.
- 5d ago First seen · 323 lines · 9 tokens per session scan A 9beebea4c965
review is a command published in the GitHub repository frenzymath/Archon (213 stars, last pushed 18d ago), licensed Apache-2.0. It adds 9 tokens to every session and 2,843 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
thoughtdag
把当前 Claude Code 会话在 ThoughtDAG 中打开（桌面版直连；无桌面版时走本机桥）.
wisp-dashboard
Open the WISP dashboard in your browser.
forkmind
Start ForkMind or branch/inspect/regression-test an LLM call.
graph-open
The web UI requires the human-only full-authority token (uitoken). It is stored in no file, so you cannot know it and must not try to find it.
graph-new
Decompose a natural-language requirement into an execution graph and register it (does not run it).
graph-lock
Guide the user through locking/unlocking a graph (only a human can do it).