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 skills add GoogilyBoogily/googilyboogily-claude-power-tools --skill architect-reviewergit 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/skills/googilyboogily/googilyboogily-claude-power-tools/architect-reviewer)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/architect-reviewer"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/architect-reviewer/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/skills/googilyboogily/googilyboogily-claude-power-tools/architect-reviewer"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/architect-reviewer.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.00039 | $0.01263 |
| Opus 5 | $0.00019 | $0.00632 |
| Sonnet 5 | $0.00008 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
architect-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 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Reviewer
Conduct a comprehensive architecture review by evaluating system designs, architectural decisions, and technology choices across five dimensions. Produce a prioritized report with actionable recommendations.
Input
$ARGUMENTS — the target path or component to review, and optionally:
--output <path>— where to write the report (default:./architecture-review.md)
If no target path is provided, ask using AskUserQuestion.
Parse Arguments
Extract from $ARGUMENTS:
- Target path: The directory or file to review
- Output path: Value after
--outputflag, or default to./architecture-review.md
Safety Rules
- NEVER modify source code — review and report only
- NEVER make changes to the codebase under review
- Evaluate decisions against requirements — not against ideal theory
- Be pragmatic: balance ideal architecture with practical constraints
Process
Phase 1: Scope and Context
- Read the target path. If it is a directory, scan its structure with Glob. If a single file, read it.
- Identify the system's purpose by reading README, CLAUDE.md, package.json, or equivalent project files.
- Detect the tech stack: languages, frameworks, databases, infrastructure.
- Identify scale requirements and constraints from documentation or configuration.
- Note the project's age and maturity (check git history with
git log --oneline -20).
CHECKPOINT — Scope Confirmation:
Present your understanding of:
- System purpose and domain
- Tech stack detected
- Scale/constraints identified
- Proposed review focus areas
Ask: "Is this scope correct? Any areas you'd like me to focus on or skip?"
Phase 2: Parallel Dimension Analysis
Load review dimensions from ${CLAUDE_SKILL_DIR}/references/review-dimensions.md.
Launch up to 5 parallel Explore agents, one per review dimension. Each agent receives:
- The target path
- The project context gathered in Phase 1
- Its specific dimension checklist from the reference file
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 156 lines · 39 tokens per session scan A 17581876e92a
architect-reviewer is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,263 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 skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…