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.
git clone --depth 1 https://github.com/moneytosms/claude-startWrote 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/moneytosms/claude-start/review)<a href="https://agentmods.dev/commands/moneytosms/claude-start/review"><img src="https://agentmods.dev/badge/commands/moneytosms/claude-start/review/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/moneytosms/claude-start/review"><img src="https://agentmods.dev/badge/commands/moneytosms/claude-start/review.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.00250 |
| Opus 5.5 | $0.00000 | $0.00100 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
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 2mo 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.
What it actually says
/review
Invoke the CodeReviewer agent on the current diff. Ask permission before spawning.
Usage
/review— review all changes on this branch vsmain/review staged— review only staged changes/review <sha>— review a specific commit
Steps
- Determine scope from the argument (default:
main..HEAD) - Run the appropriate git command to get the diff:
- Default:
git diff main..HEAD - Staged:
git diff --staged - Commit:
git show <sha>
- Default:
- Ask permission to spawn
CodeReviewer - On approval, spawn
CodeReviewerwith:- The full diff
- The list of changed files with context
- A note of what the changes are intended to do (ask me if unclear)
- Return the review report verbatim — do not edit or summarise it
Rules
- Always ask before spawning the agent
- Do not make edits based on review findings without explicit confirmation
- If the diff is empty, stop and report — nothing to review
- If there are no commits ahead of
main, stop and report
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.
- 2mo ago First seen · 31 lines · 0 tokens per session scan A 8fe56cc86749
review is a command published in the GitHub repository moneytosms/claude-start (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 250 tokens. 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-31.
Other commands, from other repositories
track
Show progress, flags and open decisions.
plan-status
Show feature plan status for the current workspace.
feature-resume
Resume implementation on an existing feature, interactively.
review
Check implementation against the feature ledger.
debug
Route a failure to the right debug methodology.
retro
Score zforge's workflow performance on a feature.