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/kastheco/claude-plugins/review-codegit clone --depth 1 https://github.com/kastheco/claude-pluginsWhat 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.00009 | $0.00251 |
| Opus 5 | $0.00005 | $0.00125 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
review-code 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.
What it actually says
/kas:review-code - Code Quality Review
Run a ruthless code review channeling Linus Torvalds philosophy.
Workflow
1. Identify scope
git status
git diff --stat
If no changes, report "Nothing to review" and stop.
2. Read agent instructions
Read agents/code-reviewer.md (relative to plugin root) and apply the review philosophy, checklist, and output format defined there.
3. Execute review
Review the changes following the agent's:
- Review philosophy (simplicity, correctness, performance, readability, error handling)
- Severity levels (Critical 91-100, High 71-90, Medium 41-70, Low 1-40)
- Review checklist
- Output format
4. Return findings
Provide structured output with:
- Overall assessment: APPROVED / NEEDS CHANGES / REJECTED
- Issues by severity with file:line references
- Positive observations
Rules
- Read-only: Never edit files
- Return structured findings, do not apply fixes
- Address all Critical and High issues before approving
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 · 44 lines · 9 tokens per session scan A 1668a797575d
review-code is a command published in the GitHub repository kastheco/claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 251 once invoked, about $0.0000 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.