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 PANYUXIN6/pyx-skills --skill using-superpowersgit clone --depth 1 https://github.com/PANYUXIN6/pyx-skillsWrote 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/panyuxin6/pyx-skills/using-superpowers)<a href="https://agentmods.dev/skills/panyuxin6/pyx-skills/using-superpowers"><img src="https://agentmods.dev/badge/skills/panyuxin6/pyx-skills/using-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/panyuxin6/pyx-skills/using-superpowers"><img src="https://agentmods.dev/badge/skills/panyuxin6/pyx-skills/using-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.00032 | $0.00412 |
| Opus 5 | $0.00016 | $0.00206 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
using-superpowers 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.
What it actually says
Route to the Right Skills
At the start of a substantive task, decide whether an available skill would materially improve how the task is performed.
Select a skill when:
- The user explicitly asks to apply it.
- The request strongly matches its description.
- It is a necessary prerequisite for another selected workflow.
Treat topic-only or weakly related mentions as source context rather than invocation. When the user asks to explain, compare, or audit skills, inspect them as source material; when the user asks to change a skill, use the relevant skill-authoring workflow.
Select the Minimum Useful Set
Prefer the smallest set of skills that fully covers the task.
Use process skills when they materially change the approach. Use domain or implementation skills for specialized knowledge and execution. When both are needed, apply them in dependency order rather than repeatedly re-routing.
After selecting skills:
- Briefly tell the user which skills are being used and why.
- Let each selected skill own its relevant workflow.
- Keep the selection for the current task and re-route only after a substantial task change.
Resolve Conflicts
Follow user instructions and repository-specific instructions over skill defaults.
When multiple skill instructions overlap, prefer the more specific instruction and keep each gate or checklist owned by one skill.
Use Judgment
A skill is useful when it changes a decision or action by adding specialized knowledge, a meaningful decision framework, a fragile procedure, or a required tool workflow. If removing the skill would leave the task's process materially unchanged, treat it as unnecessary for that task.
If context inspection shows that a selected skill changes no decision or action, release it and continue with the remaining workflow.
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 · 46 lines · 32 tokens per session scan A 8817d877f7b9
using-superpowers is a skill published in the GitHub repository PANYUXIN6/pyx-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 412 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…
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…