Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-os. 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/TheSmokeDev/taskchad-os/master/.claude/commands/validation/code-review-fix.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/thesmokedev/taskchad-os/code-review-fix)<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/code-review-fix"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/code-review-fix/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/thesmokedev/taskchad-os/code-review-fix"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/code-review-fix.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.00011 | $0.00123 |
| Opus 5.5 | $0.00004 | $0.00049 |
| Sonnet 5.5 | $0.00002 | $0.00025 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
code-review-fix 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 1mo 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
I ran/performed a code review and found these issues:
Code-review (file or description of issues): $1
Please fix these issues one by one. If the Code-review is a file read the entire file first to understand all of the issue(s) presented there.
Scope: $2
For each fix:
- Explain what was wrong
- Show the fix
- Create and run relevant tests to verify
After all fixes, run the validate command (see commands/validate.md) to finalize your fixes.
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.
- 1mo ago First seen · 18 lines · 11 tokens per session scan A 0e037ece69c9
code-review-fix is a command published in the GitHub repository TheSmokeDev/taskchad-os (28 stars, last pushed 23d ago), licensed MIT. It adds 11 tokens to every session and 123 once invoked, about $0.0000 per session on Opus 5.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
review
Manage AO code reviews of a worker's PR.
adversarial-review
Adversarial, reproduce-by-execution review of a GitHub PR (fan-out sub-agents, verify, draft review).
second-brain-mapping
Map your vault: extract structured metadata from every typed file, surface cross-doc insights, optionally build a knowledge graph.
cierre
A sales call just ended: turn its transcript into the full follow-up (CRM, tasks, email draft, reminder, coaching).
evolve
Cluster hardened instincts into a proposed Command / Skill / Agent (Instinct Engine).
insights
Weekly or monthly journal insights with pattern recognition and panel feedback.