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 tjboudreaux/cc-plugin-engineering-excellence --skill meta-superpowersgit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-engineering-excellenceWrote 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/tjboudreaux/cc-plugin-engineering-excellence/meta-superpowers)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-engineering-excellence/meta-superpowers"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-engineering-excellence/meta-superpowers/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/tjboudreaux/cc-plugin-engineering-excellence/meta-superpowers"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-engineering-excellence/meta-superpowers.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.00036 | $0.00465 |
| Opus 5 | $0.00018 | $0.00233 |
| Sonnet 5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade B, and why
meta-superpowers scanned grade B with 1 finding 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
1. ☐ Mentally enumerate available skills. What it actually says
Using Skills Effectively
Mandatory First-Response Protocol
Before responding to any user request:
- ☐ Mentally enumerate available skills.
- ☐ Ask: “Does ANY skill match this task?”
- ☐ If yes → Use the Skill tool to read/run it (do not rely on memory).
- ☐ Announce: “I’m using [Skill Name] to …”.
- ☐ Follow the skill exactly (brainstorming before coding, etc.).
Skipping this checklist is automatic failure.
Critical Rules
- Mandatory workflows – Brainstorming before coding, TDD, verification, etc. Instructions about WHAT to do never override HOW defined by skills.
- Execute via Skill tool – Always load the latest file; skills evolve.
Rationalization Triggers (STOP immediately)
- “This is simple”
- “I’ll just gather info first”
- “I remember the skill”
- “Skill is overkill”
- “Let me do one thing before checking”
These are warning signs that you’re about to skip process. Don’t.
Skills with Checklists
If a skill has a checklist, create TodoWrite items for each step. No mental tracking, no batching, no skipping. Mark complete only when done.
Announcing Skill Usage
Always tell your partner: “I’m using [Skill] to [task].”
- Promotes transparency and ensures accountability.
- Confirms you actually read the skill.
Instructions vs. Workflows
User instructions describe outcomes, not process. You still must execute brainstorming, TDD, verification, etc., unless explicitly told otherwise.
Summary
- Check for relevant skills before doing anything.
- Use the Skill tool, announce usage, follow instructions exactly.
- Convert skill checklists into TodoWrite tasks.
Failing to use applicable skills = failing the task.
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 · 52 lines · 36 tokens per session scan B fbf2eb888216
meta-superpowers is a skill published in the GitHub repository tjboudreaux/cc-plugin-engineering-excellence (4 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 465 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…