Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-toolsnpx agentmods add skills/googilyboogily/googilyboogily-claude-power-tools/generate-claude-mdWrote 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/generate-claude-md)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/generate-claude-md"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/generate-claude-md/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/generate-claude-md"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/generate-claude-md.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.00151 | $0.02515 |
| Opus 5 | $0.00076 | $0.01257 |
| Sonnet 5 | $0.00030 | $0.00503 |
| Haiku 4.5 | $0.00015 | $0.00251 |
Grade A, and why
generate-claude-md 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Distributed CLAUDE.md Hierarchy
Explore a project's codebase and generate an optimized hierarchy of CLAUDE.md files — a lean root file that acts as an index/router, plus focused sub-CLAUDE.md files in directories that need their own guidance. If CLAUDE.md files already exist, intelligently merge rather than overwrite.
Claude Code loads subdirectory CLAUDE.md files on-demand when it reads files there, so distributing context this way keeps startup lean while giving Claude rich, targeted guidance exactly when it needs it.
Input
$ARGUMENTS — optional project path (defaults to current working directory), plus flags:
--dry-run: produce the plan and show proposed content without writing any files--force: overwrite existing CLAUDE.md files instead of merging
Parse Arguments
Extract from $ARGUMENTS:
- Project path: first positional argument, or
.if not provided. Resolve to absolute path. --dry-run: boolean flag--force: boolean flag
Process
Phase 1: Initialize
-
Resolve the project path. Verify it exists and is a directory.
-
Discover existing CLAUDE.md infrastructure:
- Run
Glob("**/CLAUDE.md")from the project root to find all existing CLAUDE.md files - Run
Glob(".claude/rules/**/*.md")to find existing rules files - Read each discovered file to understand current coverage
- Run
-
Determine operating mode:
- CREATE: no CLAUDE.md files exist anywhere in the project
- UPDATE: a root CLAUDE.md and/or sub-CLAUDE.md files already exist
- HYBRID: some locations have files, others don't
-
Present findings to the user:
- List all discovered CLAUDE.md files with their line counts
- List discovered rules files
- State the operating mode
- Ask to confirm proceeding
Phase 2: Parallel Codebase Exploration
Dispatch three Agent calls in a single message using the Explore subagent type. Each agent has a focused scope to avoid duplicate work.
Agent 1 — Structure & Identity
What ships with it
3 files 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 · 223 lines · 151 tokens per session scan A 1841ac87c1d6
generate-claude-md is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 151 tokens to every session and 2,515 once invoked, about $0.0008 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…