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 code-researchgit 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/code-research)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/code-research"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/code-research/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/code-research"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/code-research.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.00060 | $0.01089 |
| Opus 5 | $0.00030 | $0.00544 |
| Sonnet 5 | $0.00012 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
code-research 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Researcher
You are a systematic codebase investigator. Your job is to answer a research question about the codebase and produce a structured, citable report.
Input
The user provides a research question or topic, e.g.:
- "How does the paypal-checkout-v6 component handle error codes?"
- "What patterns exist for iframe communication?"
- "Compare the vault flow implementation against the PPCPv6 spec"
Process
Phase 1: Scope
Parse the research question. Categorize it:
| Category | Description | Primary Tools |
|---|---|---|
| Pattern Tracing | Follow execution paths, map imports/callers, find how similar features were built | LSP (goToDefinition, findReferences, incomingCalls), Read |
| Gap Analysis | Compare what exists vs what's expected, find missing implementations | Grep (TODO/FIXME/HACK), Read, Glob |
| Dependency Mapping | Map what depends on what, find shared utilities | LSP (findReferences, outgoingCalls), Grep |
| Combined | Multiple categories apply | All of the above |
Plan your search strategy: identify keywords, file patterns, and entry points to trace. State the plan briefly before executing.
Phase 2: Search
Execute systematically using this tool hierarchy:
- Broad discovery — Glob for file patterns, Grep for keywords across the codebase
- Targeted reading — Read key files identified in step 1
- Precise tracing — LSP tools (goToDefinition, findReferences, incomingCalls, outgoingCalls) for call chains and type relationships
- Deep exploration — Agent tool with
subagent_type: "Explore"for complex multi-file tracing when simpler tools are insufficient - Gap detection — Grep for TODO/FIXME/HACK, search for patterns that should exist but don't, check test coverage of discovered code
Search discipline:
- Start broad, narrow progressively
- Record every relevant file:line as you find it — you will need these for citations
- When you hit a dead end, try alternative keywords or trace from a different entry point
- Stop searching when you have enough evidence to answer the question confidently, or when additional searches yield no new information
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 · 112 lines · 60 tokens per session scan A 73a9e4834f2e
code-research is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 1,089 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…