using-superpowers

using-superpowers is a skill for Claude Code from guanyang/open-agent-hub. It costs 28 tokens per session (735 once invoked), scanned A, a copy of using-superpowers, MIT.

A conversation-starting rule for finding and applying relevant coding-agent skills before taking action. It treats skills as required instructions when they match the task.

In plain words
What is it for?
Use it at the start of conversations and before tasks that may require specialized skills or a defined workflow.
Why use it?
It helps the agent follow the right task-specific process instead of beginning work without the relevant guidance.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

Part of the open-agent-hub plugin — 105 skills, 3 commands, 5 agents, 6 MCP servers shipped together

Good fit Use it at the start of conversations and before tasks that may require specialized skills or a defined workflow.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/guanyang/open-agent-hub/using-superpowers
Install

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.

Any agent
npx skills add guanyang/open-agent-hub --skill using-superpowers
Clone the repo
git clone --depth 1 https://github.com/guanyang/open-agent-hub

Made for: Claude Code.

Or install open-agent-hub, the plugin that ships this one along with the rest of its 105 skills, 3 commands, 5 agents, 6 MCP servers.

Wrote 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.

agentmods badge for using-superpowers

README.md
[![agentmods](https://agentmods.dev/badge/skills/guanyang/open-agent-hub/using-superpowers/github.svg)](https://agentmods.dev/skills/guanyang/open-agent-hub/using-superpowers)
Your own site
<a href="https://agentmods.dev/skills/guanyang/open-agent-hub/using-superpowers"><img src="https://agentmods.dev/badge/skills/guanyang/open-agent-hub/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.

agentmods 80×15 button for using-superpowers

Your own site · 80×15
<a href="https://agentmods.dev/skills/guanyang/open-agent-hub/using-superpowers"><img src="https://agentmods.dev/badge/skills/guanyang/open-agent-hub/using-superpowers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 735 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00735
Opus 5.5 $0.00011 $0.00294
Sonnet 5.5 $0.00006 $0.00147
Haiku 4.5 $0.00003 $0.00073

Measured 1mo ago against content hash 82c5c8866ad7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

This is a copy

100% identical to using-superpowers — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/using-superpowers/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. You cannot rationalize your way out of this.

The Rule

Invoke relevant or requested skills BEFORE any response or action — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.

Before entering plan mode: if you haven't already brainstormed, invoke the brainstorming skill first.

Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.

Skill Priority

When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Superpowers' most common process skills, but the rule holds for any of them.

  • "Let's build X" → superpowers:brainstorming first, then implementation skills.
  • "Fix this bug" → superpowers:systematic-debugging first, then domain skills.

Red Flags

These thoughts mean STOP—you're rationalizing:

Thought Reality
"This is just a simple question" Questions are tasks. Check for skills.
"I need more context first" Skill check comes BEFORE clarifying questions.
"Let me explore the codebase first" Skills tell you HOW to explore. Check first.
"I can check git/files quickly" Files lack conversation context. Check for skills.
"Let me gather information first" Skills tell you HOW to gather information.
"This doesn't need a formal skill" If a skill exists, use it.
"I remember this skill" Skills evolve. Read current version.
"This doesn't count as a task" Action = task. Check for skills.
"The skill is overkill" Simple things become complex. Use it.
"I'll just do this one thing first" Check BEFORE doing anything.
"This feels productive" Undisciplined action wastes time. Skills prevent this.
"I know what that means" Knowing the concept ≠ using the skill. Invoke it.

Read the full file on GitHub · 66 lines

Files

What ships with it

8 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.

Changes

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.

  1. 1mo ago Changed · +2 lines 82c5c8866ad7
  2. 1mo ago First seen · 64 lines · 28 tokens per session scan A 30f2ab78e20d

Subscribe to this mod's changes

using-superpowers is a skill published in the GitHub repository guanyang/open-agent-hub (980 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 735 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to using-superpowers, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

learn

Runs a six-phase research workflow from source bundle to publish-ready output. Use when researching an unfamiliar domain or compiling materials into one reference. Not for quick lookups or single-file reads.

tw93/Waza · 39 tokens

wechat-sticker-maker

A tool that cuts a grid image into separate WeChat stickers and resizes the files to WeChat’s required formats. It supports common six-, nine-, and twelve-panel layouts.

guanyang/super-publisher · 60 tokens

academic-paper-writer

A coordinating skill for planning and drafting computer science, artificial intelligence, and machine learning papers from research notes, code, literature, or venue requirements. It moves through a defined sequence of paper-writing stages.

joshua-zyy/academic-paper-writer · 87 tokens

academic-latex-layout

Use when working on academic paper LaTeX layout, figure/table float placement, draft-to-template LaTeX generation, existing .tex project layout repair, figures piling up, figures far from text, large blank areas, two-column figure/table placement, page-limit layout cleanup, or compiled PDF layout review.

joshua-zyy/academic-paper-writer · 66 tokens

software-in-worten

Übersetzt zwischen Benutzeroberfläche und Text — in beide Richtungen. Aus einer beschriebenen Oberfläche wird ein Skill; aus einem Skill wird eine Oberfläche. Nutzen, wenn eine Anwendung entworfen wird und der Ablauf noch unklar ist, wenn ein bestehendes Werkzeug als Skill verfügbar gemacht werden soll, wenn…

ellmos-ai/skills · 87 tokens

spec-archive

Fold a completed OpenSpec change into the project's specs, commit the move, and open the PR - the last link in the spec chain. Wraps /opsx:archive, which is git-blind. Use when the user says "archive the change", "archive that spec", "/spec-archive", "fold this into the specs", "close out the change", "it's done, land…

pivoshenko/pivoshenko.ai · 207 tokens