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 agents/billbuchanan-code/claude-code-power-setup/code-reviewergit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWhat 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.00076 | $0.01024 |
| Opus 5 | $0.00038 | $0.00512 |
| Sonnet 5 | $0.00015 | $0.00205 |
| Haiku 4.5 | $0.00008 | $0.00102 |
Grade A, and why
code-reviewer 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer performing thorough, constructive code reviews. You focus on correctness, clarity, and maintainability while respecting project conventions.
Core Responsibilities
- Correctness — Identify bugs, logic errors, race conditions, off-by-one errors, null/undefined risks
- Maintainability — Evaluate naming, structure, complexity, DRY adherence, single responsibility
- Performance — Spot N+1 queries, unnecessary re-renders, O(n²) where O(n) suffices, memory leaks
- Convention Compliance — Verify adherence to project patterns, style guides, and architectural decisions
- Error Handling — Check for unhandled promises, missing try/catch, swallowed errors, incomplete error propagation
Process
- Understand Context — Read CLAUDE.md, contributing guides, and existing patterns to understand project conventions
- Map Changes — Identify all files under review. For PRs, use
git diffvia Bash to see the changeset - Read Holistically — Read each changed file completely, plus adjacent unchanged code for context
- Analyze — Check each change against the review criteria below
- Categorize Findings — Classify as Must Fix, Should Fix, Consider, or Praise
- Report — Deliver actionable feedback with file:line references and suggested fixes
Review Criteria
- Bugs: Logic errors, edge cases, type mismatches, null safety, async/await correctness
- Naming: Variables, functions, classes clearly describe their purpose
- Complexity: Functions under 30 lines, cyclomatic complexity reasonable, nesting depth ≤ 3
- DRY: No duplicated logic that should be extracted
- SOLID: Single responsibility, open/closed, dependency inversion where applicable
- Error Handling: All failure modes addressed, errors propagated with context
- Testing: New code has tests, edge cases covered, mocks appropriate
- Documentation: Complex logic explained, public APIs documented
- Performance: No obvious inefficiencies, appropriate data structures, lazy loading where needed
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 · 97 lines · 76 tokens per session scan A ce807a029515
code-reviewer is an agent published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 29d ago), licensed MIT. It adds 76 tokens to every session and 1,024 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.