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/mckruz/claude-code-mastery/code-reviewgit clone --depth 1 https://github.com/MCKRUZ/claude-code-masteryWhat 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.00024 | $0.00290 |
| Opus 5 | $0.00012 | $0.00145 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
/code-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 2d 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
Code Review
Perform a comprehensive security and quality review of uncommitted changes.
Workflow
-
Get changed files:
git diff --name-only HEAD -
For each changed file, check for:
Security Issues (CRITICAL)
- Hardcoded credentials, API keys, tokens
- SQL injection vulnerabilities
- XSS vulnerabilities
- Missing input validation
- Insecure dependencies
- Path traversal risks
Code Quality (HIGH)
- Functions > 50 lines
- Files > 800 lines
- Nesting depth > 4 levels
- Missing error handling
- console.log statements
- TODO/FIXME comments
- Missing JSDoc for public APIs
Best Practices (MEDIUM)
- Mutation patterns (use immutable instead)
- Emoji usage in code/comments
- Missing tests for new code
- Accessibility issues (a11y)
Output Format
- Generate report with:
- Severity: CRITICAL, HIGH, MEDIUM, LOW
- File location and line numbers
- Issue description
- Suggested fix
Gate
- Block commit if CRITICAL or HIGH issues found — list all issues that must be resolved before merging.
Never approve code with security vulnerabilities.
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.
- 2d ago First seen · 52 lines · 24 tokens per session scan A 270de5cc240e
/code-review is a command published in the GitHub repository MCKRUZ/claude-code-mastery (11 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 290 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
claude-md-migrate
Rewrite a bloated or stale CLAUDE.md into a lean, verified "map, not wishes" file — nothing invented, hard rules preserved verbatim.
claude-md-new
Scaffold a CLAUDE.md for this repo from battle-tested templates, filled in with the project's real commands.
claude-md-audit
Grade this repo's CLAUDE.md / AGENTS.md (0–100) and return a worst-first fix list.
review
请从风险、回归、测试遗漏和可读性四个角度 review 当前变更。.
explain
请解释当前文件或目录的核心结构，并指出我下一步应该看哪里。.
fix
请先定位根因，再给出最小修改方案，最后说明验证方式。.