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/plugins/googilyboogily/googilyboogily-claude-power-tools/code-quality)<a href="https://agentmods.dev/plugins/googilyboogily/googilyboogily-claude-power-tools/code-quality"><img src="https://agentmods.dev/badge/plugins/googilyboogily/googilyboogily-claude-power-tools/code-quality/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/plugins/googilyboogily/googilyboogily-claude-power-tools/code-quality"><img src="https://agentmods.dev/badge/plugins/googilyboogily/googilyboogily-claude-power-tools/code-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-quality 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 8d 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.
What it actually says
{
"name": "code-quality",
"description": "Code review, dead code detection, and validate-and-fix commands for maintaining code quality",
"version": "1.0.0",
"author": {
"name": "GoogilyBoogily"
}
}
What it installs
The manifest is a name and a version. 3 commands travel with it, and installing the plugin installs all of them — 45 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 8d ago First seen · 9 lines scan A 873ac53eb270
code-quality is a plugin published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
code-review
Perform a comprehensive code review of recent changes.
kin
Kin keeps a living map of the software itself so humans and agents can understand what every change touches. Locate, search, context packs, data-flow tracing, and impact analysis without raw file search.
double-check
Verify code correctness with systematic second-pass analysis.
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
memtrace-skills
Memtrace skills for codebase exploration, code search, relationship analysis, temporal evolution, blast radius impact, code quality, graph algorithms, API topology, GitHub PR code review, multi-agent fleet coordination (branch-scoped intents, conflict classification, and agent-judged Class C resolution), and…
tidy
Careful low-risk codebase cleanup across 7 focused tracks: deduplication, type consolidation, dead code removal, circular dependency untangling, type strengthening, error-handling cleanup, and deprecated/AI-slop removal. Each track inspects, writes a critical assessment, ranks proposed changes by confidence, and…