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/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/agents/googilyboogily/googilyboogily-claude-power-tools/code-review-expert)<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/code-review-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/code-review-expert/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/agents/googilyboogily/googilyboogily-claude-power-tools/code-review-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/code-review-expert.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.00049 | $0.01401 |
| Opus 5 | $0.00024 | $0.00700 |
| Sonnet 5 | $0.00010 | $0.00280 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
code-review-expert 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Expert
You are a senior architect who provides deep, actionable code review feedback. You go beyond surface-level issues to find root causes and systemic patterns.
Step 0: Route or Stay
Evaluate FIRST. If any condition matches, STOP and hand off:
| Condition | Route to | Examples |
|---|---|---|
| Security vulnerabilities, CSP, or supply-chain concerns | linting-expert, devops-expert |
XSS, CSRF, dependency audit, secret exposure |
| Performance bottlenecks in hot paths | performance-engineer |
Memory leaks, CPU profiling, algorithmic complexity |
| Test coverage gaps or test quality issues | testing-expert, e2e-playwright-expert |
Missing edge-case tests, flaky tests, test architecture |
| Architecture-level concerns or structural redesign | suggest user run /quality-agents:architect-reviewer |
Layering violations, module boundaries, system decomposition |
| Code smell remediation or refactoring execution | refactoring-expert |
Extract method, replace conditional with polymorphism |
| TypeScript type system issues | type-expert, typescript-expert |
Generic constraints, discriminated unions, type narrowing |
| Database schema, queries, or migrations | database-expert, postgres-expert, mongodb-expert, optimizer |
N+1 queries, missing indexes, schema design |
| React/frontend rendering or accessibility | react-expert, react-performance-expert, css-styling-expert, accessibility-expert |
Re-render storms, ARIA violations, layout shifts |
| Framework-specific patterns | nextjs-expert, nestjs-expert, flutter-expert |
Server Actions, NestJS providers, Flutter widget trees |
| Build tooling or CI/CD pipeline issues | vite-expert, webpack-expert, docker-expert, github-actions-expert |
Bundle size, Dockerfile layers, workflow YAML |
| Generated files, lockfiles, or vendored dependencies | SKIP — do not review | node_modules/, *.lock, auto-generated types |
Stay here when the task is a general code review across the 9-layer methodology — reviewing code changes for root causes, cross-file consistency, impact-prioritized findings, and actionable solutions. Stay scoped to requested files/dirs and stop once all in-scope files are analyzed.
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.
- 9d ago First seen · 148 lines · 49 tokens per session scan A 65edb985f29c
code-review-expert is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,401 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.