Borrowing it
Nothing to install: this file belongs to flowing-abyss/obsidian-hybrid-search. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/flowing-abyss/obsidian-hybrid-search/master/.ai/skills/using-superpowers/SKILL.mdgit clone --depth 1 https://github.com/flowing-abyss/obsidian-hybrid-searchWrote 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/flowing-abyss/obsidian-hybrid-search/using-superpowers)<a href="https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/using-superpowers"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/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/flowing-abyss/obsidian-hybrid-search/using-superpowers"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/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.01195 |
| Opus 5.5 | $0.00011 | $0.00478 |
| Sonnet 5.5 | $0.00006 | $0.00239 |
| Haiku 4.5 | $0.00003 | $0.00120 |
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 today.
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 — 78 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.
This template's additional skills
This template vendors four skills beyond stock Superpowers. They aren't a separate system , they slot into the same process/implementation ordering above, at these points:
| Trigger | Skill | Where it sits |
|---|---|---|
| An unfamiliar or version-sensitive API, a new dependency, a library/framework upgrade, a deprecated/experimental API, or existing code that looks incompatible with current docs , not routine use of an API already established in the codebase | source-driven-development |
Runs during writing-plans' applicability pass and alongside implementation , cites official docs instead of implementing from memory. Verifies API usage; does not override an approved spec/plan or existing project conventions. |
| A new user-triggered or background operation could fail without a clear message or diagnostics, an existing silent catch/unhandled rejection, or a new failure boundary with no established project pattern yet | handling-utility-failures |
Part of implementation, before finishing-a-development-branch , visible errors ship with the feature, not after. Not for routine I/O repeating an already-established pattern. |
| A change touches an external or persisted contract (settings/data format, a public API/command, a user-facing feature needing a compatibility path) , not internal refactoring or dead-code removal | deprecation-and-migration |
Runs before brainstorming on contract-changing requests, to answer the five questions (what's changing, what depends on it, migration/fallback, rollback, safe-removal timing) , design approval and planning still go through brainstorming → writing-plans afterward. Not a replacement for either. |
| Cutting a release , bumping the version, tagging, publishing | releasing-an-npm-package |
A separate, self-contained flow after finishing-a-development-branch, run only on an explicit release request , not part of the build loop and never triggered automatically by finishing a branch. |
What ships with it
6 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.
- today First seen · 78 lines · 28 tokens per session scan A 64c265188496
using-superpowers is a skill published in the GitHub repository flowing-abyss/obsidian-hybrid-search (113 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,195 once invoked, about $0.0001 per session on Opus 5.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-10-24.
Other skills, from other repositories
codemark
Manage structural code bookmarks that survive refactoring. Use when the user says "remember this", "bookmark this", "save this location", "load my bookmarks", "what do I have bookmarked", "mark this code", "codemark", or when starting a new session and needing to reload context from a previous session. Also use…
qdrant-vector-search
High-performance vector similarity search engine for RAG and semantic search. Use when building production RAG systems requiring fast nearest neighbor search, hybrid search with filtering, or scalable vector storage with Rust-powered performance.
notebrain-assistant
Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like…
palaia-memory
Check this person's shared memory before answering anything about their own work, and add to it when something is worth keeping. It holds their projects, decisions and reasons, house conventions (naming, commit messages, tests, releases, review and escalation), people and hard-won details, and every AI tool they use…
palaia-messenger
Register this session with the shared directory so other AI sessions and this person's dashboard can see what you are doing, then use it to reach another live session directly instead of relaying everything through the person. Use it at the start of a task, before picking one up, when your work depends on or informs…
palaia-capture
Save what this person tells you into their shared memory, which every AI tool they use can read. Use it the moment they state a decision and the reason for it, a convention, a correction, or a detail that was expensive to work out — including when they mention it in passing on the way to a different question. Save it…