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 adr-gathergit 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/adr-gather)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/adr-gather"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/adr-gather/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/adr-gather"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/adr-gather.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.00050 | $0.02168 |
| Opus 5 | $0.00025 | $0.01084 |
| Sonnet 5 | $0.00010 | $0.00434 |
| Haiku 4.5 | $0.00005 | $0.00217 |
Grade A, and why
adr-gather 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Context Gathering — Compiler Mode
Compile all context needed to write an Architecture Decision Record. In the full pipeline, this skill receives a decisions file (from adr-discuss) and a research file (from arch-research), merges them, fills any gaps with targeted questions, and produces the final context file that adr-generate consumes.
Can also run standalone — if no decisions file is provided, falls back to direct Q&A mode (compatible with v2 behavior).
Input
$ARGUMENTS — path to a decisions file, and optionally --research <path> for the research file.
Parse for:
- Decisions path —
docs/context/decisions/<name>-decisions.md(first positional arg or detected from path) - Research path —
--research <path>pointing to the RESEARCH.md file - Topic — if no files provided, treated as a topic string for standalone mode
Source Integrity Rules
Every factual claim in the context file must be traceable to research performed in this session.
- Cite your work. When referencing code, patterns, conventions, or architectural details, cite the specific tool call that discovered it (file path + line number from Read, Grep result, Explore agent finding).
- Never reference prior Claude sessions or Claude memory. Do not use phrases like "from our previous conversation," "as we discussed before," "based on prior analysis." Each context file stands on its own.
- Assumptions are labeled, not hidden. If you lack evidence for a claim, label it explicitly in the Open Questions section.
Process
Human-in-the-loop: Never proceed past a decision point without user approval.
Mode Detection
Check if $ARGUMENTS points to a decisions file:
- If YES → Compiler Mode (Phase 1-4 below)
- If NO → Standalone Mode (Phase S1-S5 below)
Compiler Mode (with decisions + optional research)
Phase 1: Load Inputs
- Read the decisions file. Extract:
- All D-XX decisions (User Decisions + Claude's Discretion)
- Prior Constraints
- Deferred Ideas
- Open Questions
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 · 270 lines · 50 tokens per session scan A 4d51eafd2fbb
adr-gather is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 2,168 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-09-03.
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…