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/naimkatiman/continuous-improvement/simplicity-reviewgit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/simplicity-review)<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/simplicity-review"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/simplicity-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.1 | $0.00053 | $0.00429 |
| Opus 5 | $0.00026 | $0.00215 |
| Sonnet 5 | $0.00011 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
simplicity-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.
What it actually says
/simplicity-review — Judge the Diff Before You Ship It
Read the current change like the laziest senior dev in the room: could this have been smaller? Passing tests prove correctness, not minimality. Backed by the simplicity-review skill.
What it does
Takes the working-tree diff (vs HEAD by default; accepts an optional commit range or file list), reads each changed block, and walks a fixed reuse ladder:
1. Does this need to exist? -> skip it (YAGNI)
2. Already in this codebase? -> reuse it
3. Stdlib does it? -> use it
4. Native platform feature? -> use it
5. Installed dependency? -> use it
6. One line? -> one line
7. Only then: the minimum that works
It reports file:line, what is over-built, the specific simpler path, and closes with GO (already minimal) or TRIM (findings to apply). It does not edit code.
Default skeptical
A finding is a hypothesis. Read the surrounding code and prove the simpler path exists and preserves behavior before asserting it; a wrong trim is worse than the over-build. Never flag input validation, data-loss-preventing error handling, security, or accessibility — lazy, not negligent.
Pairs with
simplicity-reviewskill — the discipline this command runs.proceed-with-the-recommendation— apply the trims under the 7 Laws.verification-loop— the ladder to re-run on whatever you trim.production-readiness-review— the sibling diff review for performance, security, UI, and test coverage.
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 · 36 lines · 53 tokens per session scan A 339b0c4c8eb0
simplicity-review is a command published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 10d ago), licensed MIT. It adds 53 tokens to every session and 429 once invoked, about $0.0003 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-31.
Other commands, from other repositories
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
release
Generate changelog, bump version, and create git tag.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
analyze-and-create-issue
Analyze codebase and create GitHub/GitLab/Forgejo issues per finding.
generate-report
Generate a professional HTML report from assessment results in the conversation.
data-flow-analysis
Trace how data flows through the system from input to output.