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/filip-podstavec/claude-leverage/code-reviewgit clone --depth 1 https://github.com/Filip-Podstavec/claude-leverageWhat 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.00025 | $0.00678 |
| Opus 5 | $0.00013 | $0.00339 |
| Sonnet 5 | $0.00005 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Status: !git status --short
Staged shortstat: !git diff --cached --shortstat
Unstaged shortstat: !git diff --shortstat
Recent commits: !git log --oneline -5
Your role
You are orchestrating a two-phase code review:
- Phase 1: a Sonnet-based subagent reviews the code and returns structured findings.
- Phase 2: you (the main session) apply approved fixes.
You do NOT review the code yourself. The subagent does that. Your job is to delegate, summarize, get user direction, and then make changes.
Workflow
-
Determine review scope:
- If
$ARGUMENTScontains file paths, review those. - Otherwise, if there are staged changes, review the staged diff.
- Otherwise, if there are unstaged changes, review those.
- If nothing is changed, ask the user what they want reviewed.
- If
-
Capture session-decisions context (recommended for non-trivial sessions). If you made non-obvious choices during this session that the subagent could waste output re-litigating, capture them as 2-5 lines of explicit constraints to pass alongside the diff. Examples:
- "Chose REST over GraphQL — team alignment, do not suggest GraphQL"
- "Skipped retry logic — handled at gateway, do not flag missing retries"
- "Used pattern X to match existing code in src/foo/, not the more 'idiomatic' Y"
Do NOT pass full session history. If no such non-obvious decisions exist, skip this step. The point is to prevent wasted review effort on already-settled questions, not to bias the review's independence.
-
Invoke the
code-reviewersubagent with the scope and (if step 2 produced any) the constraints block. Wait for its structured report. -
Present findings to the user. Keep your summary concise. Use the subagent's priority sections (Critical / Important / Nice to have). Do not editorialize - the subagent already prioritized.
-
Ask for direction. Offer these options:
- Apply all critical and important findings
- Apply specific findings (user picks which)
- Skip fixes, the user will handle it
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.
- yesterday First seen · 57 lines · 25 tokens per session scan A c3e637b3f254
code-review is a command published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 28d ago), licensed MIT. It adds 25 tokens to every session and 678 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
new-hook
Scaffold a new Claude Code hook end-to-end — recipe-driven hook file, payload fixtures, runner, and settings.json registration with diff preview.
build-hook
Interactive guide for creating custom hooks with Q&A workflow and automatic validation.
multi-mind-zen
Execute a multi-specialist collaborative analysis where every subagent delegates all substantive work to the three zen tools: mcpzenchat, mcpzenconsensus, and mcpzenanalyze.
README
Git workflow and quality assurance commands for the claude-skills repository.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
session-end
I'll summarize this coding session and update the memory system with our accomplishments.