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 skill-creategit 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/skill-create)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/skill-create"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/skill-create/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/skill-create"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/skill-create.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.00043 | $0.01684 |
| Opus 5 | $0.00022 | $0.00842 |
| Sonnet 5 | $0.00009 | $0.00337 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
skill-create 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creation
Author a new Claude Code skill through interactive requirements gathering, codebase research, and official documentation consultation. Produces a complete skill directory with SKILL.md and optional reference files.
Input
$ARGUMENTS — a skill name or description, and optionally a location flag:
--project— create in.claude/skills/(shared with team)--user— create in~/.claude/skills/(personal, all projects)--plugin <name>— create in a plugin'sskills/directory
Parse Arguments
Extract from $ARGUMENTS:
- Name/Description: The non-flag text
- Location Flag:
--project,--user, or--plugin <name>
If no location flag is provided, ask the user in Phase 1.
Source Integrity Rules
Every design decision must be traceable to user answers, codebase research, or official documentation.
- Cite codebase findings with file:line references.
- Cite documentation with URLs.
- Label assumptions explicitly — do not present guesses as facts.
Process
Phase 1: Understand Intent
- If only a name was provided (no description), ask what the skill should do.
- Classify the skill type:
- Task skill — Procedural workflow with phases, user interaction, explicit invocation (
disable-model-invocation: true) - Reference skill — Knowledge/context provider, auto-triggered by description matching (
user-invocable: false)
- Task skill — Procedural workflow with phases, user interaction, explicit invocation (
- If no location flag provided, ask using AskUserQuestion:
- Project level (
.claude/skills/) — shared with team via version control - User level (
~/.claude/skills/) — personal, works across all projects - Plugin (
plugins/<name>/skills/) — part of a distributable plugin
- Project level (
CHECKPOINT — Confirm Understanding: Present your understanding of:
- What the skill does
- Skill type (task vs reference)
- Target location
- Expected invocation pattern
Ask: "Is my understanding correct? Anything to adjust before I gather detailed requirements?"
Phase 2: Gather Requirements
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.
- 12d ago First seen · 186 lines · 43 tokens per session scan A a322ca7de5a6
skill-create is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,684 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-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…