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/commands/googilyboogily/googilyboogily-claude-power-tools/code-review)<a href="https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/code-review"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/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/googilyboogily/googilyboogily-claude-power-tools/code-review"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/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.02170 |
| Opus 5 | $0.00006 | $0.01085 |
| Sonnet 5 | $0.00002 | $0.00434 |
| Haiku 4.5 | $0.00001 | $0.00217 |
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 12d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Current Repository State
!git status --short && echo "---" && git diff --stat && echo "---" && git log --oneline -5
Pre-Review Analysis: Think This Through End-to-End
Before launching review agents, analyze the complete impact and context:
Impact Assessment
- System Impact: What systems, services, or components could be affected by these changes?
- Deployment Context: What's the risk level and timeline for these changes?
- Integration Points: Are there external dependencies, APIs, or team workflows involved?
- Stakeholder Impact: Who depends on the code being reviewed?
Review Strategy Coordination
Based on impact assessment and $ARGUMENTS, determine:
- Critical vs. Nice-to-Have: Which review aspects are CRITICAL vs. optional for this change?
- Potential Conflicts: Could findings from different review areas suggest competing solutions?
- Shared Context: What context should all review agents be aware of?
- Appropriate Rigor: What level of analysis matches the change scope and risk?
Review Strategy
Based on $ARGUMENTS and the impact assessment above, determine which review agents are needed:
If reviewing "changes" or recent modifications:
- Analyze the file types that have been modified
- Launch only relevant review agents:
- Documentation files only (*.md, *.txt, README): Launch only Documentation & API Review agent
- Test files only (test., .spec., tests/): Launch Testing Quality Review and Code Quality Review agents
- Config files only (*.json, *.yaml, *.toml, .*rc): Launch Security & Dependencies Review and Architecture Review agents
- Source code files (*.ts, *.js, *.py, etc.): Launch all 6 review agents
- Mixed changes: Launch agents relevant to each file type present
If reviewing a specific directory or broad scope:
- Launch all 6 review agents for comprehensive coverage
Use the Task tool to invoke the appropriate code-review-expert agents concurrently with enhanced thinking trigger instructions:
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.
- 12d ago First seen · 222 lines · 12 tokens per session scan A 50f314ae2cfe
code-review is a command published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 2,170 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-31.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
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 }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.