Borrowing it
Nothing to install: this file belongs to doncheli/don-cheli-sdd. 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/doncheli/don-cheli-sdd/main/.opencode/commands/doncheli-review.mdgit clone --depth 1 https://github.com/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/doncheli-review)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/doncheli-review"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/doncheli-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/doncheli/don-cheli-sdd/doncheli-review"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/doncheli-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.00021 | $0.00067 |
| Opus 5 | $0.00010 | $0.00034 |
| Sonnet 5 | $0.00004 | $0.00013 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
doncheli-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 11d 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
Run a comprehensive peer review across 7 dimensions. Check TDD compliance, coverage >= 85%, stub detection, SOLID principles, and security.
$ARGUMENTS
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.
- 11d ago First seen · 8 lines · 21 tokens per session scan A 76f866a5aa7b
doncheli-review is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 67 once invoked, about $0.0001 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
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
review
Run a code review on changed files (or a path you pass).
differential-audit
Audit EARS↔code coherence via a bidirectional differential. With no arguments, opens a scoping conversation that interprets what the user wants audited, maps it to arrows, and captures an explicit EARS selection. With one or more EARS IDs, audits those specs directly using configured defaults. Requires docs/arrows/…
analyze
A command that examines a codebase’s Git history and file structure to find coding patterns and team habits, then records them as reusable documentation.
amby.converge
Check the codebase against spec, plan, and tasks after implementing; append gap tasks, never edit code.
review
You are a helpful coding expert. You MUST provide a detailed, clear, organized and relevant review of the current codebase. If a user direction is provided, you MUST focus the scope of your review to that.