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 Leodorareluctant259/superpowers-zh --skill using-superpowersgit clone --depth 1 https://github.com/Leodorareluctant259/superpowers-zhWrote 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/leodorareluctant259/superpowers-zh/using-superpowers)<a href="https://agentmods.dev/skills/leodorareluctant259/superpowers-zh/using-superpowers"><img src="https://agentmods.dev/badge/skills/leodorareluctant259/superpowers-zh/using-superpowers.svg" alt="Measured on agentmods" 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.00038 | $0.01677 |
| Opus 5 | $0.00019 | $0.00839 |
| Sonnet 5 | $0.00008 | $0.00335 |
| Haiku 4.5 | $0.00004 | $0.00168 |
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 8d 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
86% identical to using-superpowers — 6 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
如果一个技能适用于你的任务，你没有选择。你必须使用它。
这不可协商。这不是可选的。你不能通过合理化来逃避。
指令优先级
Superpowers 技能覆盖默认系统提示行为，但用户指令始终具有最高优先级：
- 用户的明确指令（CLAUDE.md、GEMINI.md、AGENTS.md、直接请求）——最高优先级
- Superpowers 技能 ——在冲突处覆盖默认系统行为
- 默认系统提示 ——最低优先级
如果 CLAUDE.md、GEMINI.md 或 AGENTS.md 说"不要使用 TDD"，而某个技能说"始终使用 TDD"，遵循用户的指令。用户拥有控制权。
如何访问技能
在 Claude Code 中： 使用 Skill 工具。当你调用一个技能时，其内容会被加载并呈现给你——直接遵循即可。绝不要用 Read 工具读取技能文件。
在 Gemini CLI 中： 技能通过 activate_skill 工具激活。Gemini 在会话开始时加载技能元数据，并按需激活完整内容。
在其他环境中： 查看你的平台文档了解技能的加载方式。
平台适配
技能使用 Claude Code 的工具名称。非 CC 平台：查看 references/codex-tools.md（Codex）了解工具对应关系。Gemini CLI 用户通过 GEMINI.md 自动获得工具映射。
使用技能
规则
在任何响应或操作之前调用相关或被请求的技能。 哪怕只有 1% 的可能性某个技能适用，你都应该调用该技能来检查。如果调用后发现技能不适合当前情况，你不需要使用它。
digraph skill_flow {
"收到用户消息" [shape=doublecircle];
"即将进入 EnterPlanMode？" [shape=doublecircle];
"已经头脑风暴过？" [shape=diamond];
"调用头脑风暴技能" [shape=box];
"可能有技能适用？" [shape=diamond];
"调用 Skill 工具" [shape=box];
"宣布：'使用 [技能] 来 [目的]'" [shape=box];
"有检查清单？" [shape=diamond];
"为每个条目创建 TodoWrite 待办" [shape=box];
"严格遵循技能" [shape=box];
"响应（包括澄清）" [shape=doublecircle];
"即将进入 EnterPlanMode？" -> "已经头脑风暴过？";
"已经头脑风暴过？" -> "调用头脑风暴技能" [label="否"];
"已经头脑风暴过？" -> "可能有技能适用？" [label="是"];
"调用头脑风暴技能" -> "可能有技能适用？";
"收到用户消息" -> "可能有技能适用？";
"可能有技能适用？" -> "调用 Skill 工具" [label="是，哪怕只有 1%"];
"可能有技能适用？" -> "响应（包括澄清）" [label="确定不适用"];
"调用 Skill 工具" -> "宣布：'使用 [技能] 来 [目的]'";
"宣布：'使用 [技能] 来 [目的]'" -> "有检查清单？";
"有检查清单？" -> "为每个条目创建 TodoWrite 待办" [label="是"];
"有检查清单？" -> "严格遵循技能" [label="否"];
"为每个条目创建 TodoWrite 待办" -> "严格遵循技能";
}
红线
这些想法意味着停下——你在合理化：
| 想法 | 现实 |
|---|---|
| "这只是一个简单的问题" | 问题就是任务。检查技能。 |
| "我需要先了解更多上下文" | 技能检查在澄清性问题之前。 |
| "让我先探索一下代码库" | 技能告诉你如何探索。先检查。 |
| "我可以快速查一下 git/文件" | 文件缺少对话上下文。检查技能。 |
| "让我先收集信息" | 技能告诉你如何收集信息。 |
| "这不需要正式的技能" | 如果技能存在，就使用它。 |
| "我记得这个技能" | 技能会迭代更新。阅读当前版本。 |
| "这不算一个任务" | 行动 = 任务。检查技能。 |
| "技能太小题大做了" | 简单的事会变复杂。使用它。 |
| "让我先做这一件事" | 在做任何事之前先检查。 |
| "这样做感觉很高效" | 无纪律的行动浪费时间。技能防止这一点。 |
| "我知道那是什么意思" | 知道概念 ≠ 使用技能。调用它。 |
What ships with it
2 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.
- 8d ago First seen · 135 lines · 38 tokens per session scan A f350c511f289
using-superpowers is a skill published in the GitHub repository Leodorareluctant259/superpowers-zh (5 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,677 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to using-superpowers, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
ainb-fleet:daemons
Runtime-health view of the four fleet daemons — phone bridge, notifyd, ATC, and the fleet auto-continue daemon — in one table. Each row reports state (running / stopped / unknown), pid, uptime, last activity, error count, and a HEALTH reason that distinguishes a clean stop from a crash (stale heartbeat) or a…
ainb-fleet
Fleet orchestration overview — the ainb fleet ... Rust subcommand namespace for driving every claude session on the host. Routes to the sub-skills (ainb-spawn / standup / broadcast / sequence / needs / daemon / atc). Invoke this for an at-a-glance map of what fleet can do; reach for the specific sub-skill for the verb…
ainb-fleet:bridge
Native phone bridge — relay messages two-way between a chat channel (Telegram, Slack, and/or Discord) and your ainb sessions. Inbound chat messages route to a target session (by name: prefix, else a conductor- first default) and are delivered via tmux send-keys; the session's reply is captured from its JSONL…
ainb-fleet:daemon
Long-running watcher that scans every claude session every 5s and auto-sends continue to any session whose recent tmux pane buffer matches a known API-error regex (ratelimited, overloadederror, internalservererror, requesttimeout, sockethangup, fetchfailed, ECONNRESET). Use this when you want unattended recovery from…
ainb-fleet:standup
Show fleet status — every claude session running on the host, merged across ainb + claude-peers broker + background jobs. Use when you need to enumerate sessions before composing an action, check the summary of each session, or pipe the list into jq for filtering. (Writes go via tmux by default; a peerid is just an…
ainb-fleet:cost
Show fleet spend — per-session, per-model, per-day, and per-group USD cost rollups for every claude/codex session, sourced live from ainb's burndown analytics (which already prices every provider call). Use when you need spend visibility across a multi-session fleet, want to find the most expensive session/model, or…