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.
git clone --depth 1 https://github.com/blencorp/claude-code-kitWrote 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/blencorp/claude-code-kit/code-review)<a href="https://agentmods.dev/commands/blencorp/claude-code-kit/code-review"><img src="https://agentmods.dev/badge/commands/blencorp/claude-code-kit/code-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/blencorp/claude-code-kit/code-review"><img src="https://agentmods.dev/badge/commands/blencorp/claude-code-kit/code-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.00012 | $0.00496 |
| Opus 5.5 | $0.00005 | $0.00198 |
| Sonnet 5.5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade B, and why
code-review scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!cat "$CLAUDE_PROJECT_DIR/.claude/tsc-cache"/*/edited-files.log 2>/dev/null | awk -F: '{print $2}' | sort -u || echo "No files modified yet" How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code reviewer focused on quality, best practices, and system integration.
Context
Files modified this session (auto-generated):
!cat "$CLAUDE_PROJECT_DIR/.claude/tsc-cache"/*/edited-files.log 2>/dev/null | awk -F: '{print $2}' | sort -u || echo "No files modified yet"
User-specified additional files: $ARGUMENTS
Your Task
Review the code changes for:
-
Best Practices Adherence
- Code follows project patterns and conventions
- Proper error handling and logging
- Appropriate use of TypeScript types
- No code duplication or anti-patterns
-
Architectural Consistency
- Follows layered architecture (routes → controllers → services → repositories)
- Proper dependency injection usage
- Correct placement in project structure
- Integration with existing systems
-
Code Quality
- Clear, self-documenting code
- Appropriate comments where needed
- Performance considerations
- Security best practices
-
Testing Coverage
- Identify missing test cases
- Suggest edge cases to test
- Verify testability of new code
Instructions
- Read the modified files from the auto-detected list and any user-specified files
- Examine the implementation against project guidelines (check for SKILL.md files in .claude/skills/)
- Use the Task tool to launch the code-architecture-reviewer agent with:
- subagent_type:
code-architecture-reviewer - description:
review code changes - prompt: List all modified files and ask the agent to review them for:
- Code quality issues
- Architectural concerns
- Suggested improvements
- Missing error handling or validation
- Testing gaps
- subagent_type:
- Summarize the agent's findings and create actionable recommendations
Quality Standards
- Be specific about issues found (include file paths and line numbers)
- Explain WHY something is an issue, not just WHAT
- Provide concrete examples of how to fix issues
- Prioritize findings (critical, important, nice-to-have)
- Acknowledge good practices observed
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 · 66 lines · 12 tokens per session scan B 334abcd960ff
code-review is a command published in the GitHub repository blencorp/claude-code-kit (107 stars, last pushed 10mo ago), licensed MIT. It adds 12 tokens to every session and 496 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.