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 JustMichael-80/MasterVault --skill using-superpowersgit clone --depth 1 https://github.com/JustMichael-80/MasterVaultWrote 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/justmichael-80/mastervault/using-superpowers)<a href="https://agentmods.dev/skills/justmichael-80/mastervault/using-superpowers"><img src="https://agentmods.dev/badge/skills/justmichael-80/mastervault/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/justmichael-80/mastervault/using-superpowers"><img src="https://agentmods.dev/badge/skills/justmichael-80/mastervault/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.00028 | $0.00701 |
| Opus 5.5 | $0.00011 | $0.00280 |
| Sonnet 5.5 | $0.00006 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
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.
This is a copy
98% identical to using-superpowers — 3 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.
How it starts
The opening of the file, as written. The whole thing — 63 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. |
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.
- 1mo ago First seen · 63 lines · 28 tokens per session scan A 55379fe7c1c4
using-superpowers is a skill published in the GitHub repository JustMichael-80/MasterVault (12 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 701 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to using-superpowers, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
memorb-conventions
A set of base rules for organizing a memOrb vault, including paths, folders, names, YAML frontmatter, and orb layouts. YAML frontmatter is structured information placed at the top of a text file.
dream-studio
The dream studio: once a month, use the Memory Commit Journal in memorbs/log.md to select source orbs, find recurring themes, propose new Core orbs and new or revised Belief orbs, refresh the current-state narrative on each Island, and finally rotate the journal. Sole executor of Evaluate, the last step of the…
island-reclamation
The full procedure for adding an Island (a domain of long-term responsibility or interest): first agree with the user on what the Island is and at what level to name it, then pick a folder structure, then get the first batch of files confirmed — and only then create anything, finishing with a memory-layer sync.…
memorb-lint
Wiki Lint workflow: a health check over the memory vault that surfaces contradictions, stale pages, orphans, missing pages, broken wikilinks, and bare internal paths. Offer to run it before dream-studio or after manual moves/renames. Triggers: tidy up memory, check the second brain, health check, fix links, moved…
writing-memorb-skills
A meta-skill for creating or changing smaller skills in a shared collection, including their names, metadata, structure, registration, and tests.
memorb-domain-query
Use when querying companies, employees, or contacts by email address, domain name, or company name, or when integrating Outlook/M365 email collection and company email status checks.