superpowers-zh is a Chinese community edition of superpowers, a collection of practical skills and development methods for AI coding tools. It helps users apply workflows such as brainstorming, test-driven development, debugging, code review, and other programming tasks across supported coding agents. The catalogue add-ons are the project's translated and original skills, instructions, hook, and plugin components.
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 jnMetaCode/superpowers-zh --skill diagnosing-superpowersgit clone --depth 1 https://github.com/jnMetaCode/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/jnmetacode/superpowers-zh/diagnosing-superpowers)<a href="https://agentmods.dev/skills/jnmetacode/superpowers-zh/diagnosing-superpowers"><img src="https://agentmods.dev/badge/skills/jnmetacode/superpowers-zh/diagnosing-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/jnmetacode/superpowers-zh/diagnosing-superpowers"><img src="https://agentmods.dev/badge/skills/jnmetacode/superpowers-zh/diagnosing-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.00111 | $0.02007 |
| Opus 5.5 | $0.00044 | $0.00803 |
| Sonnet 5.5 | $0.00022 | $0.00401 |
| Haiku 4.5 | $0.00011 | $0.00201 |
Grade A, and why
diagnosing-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 18d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
诊断 Superpowers
概述
和你的人类伙伴一起明确一次会话到底哪里出了问题，读取磁盘上的会话记录（transcript）， 用证据报告发生了什么。你负责报告，不负责诊断 superpowers。superpowers 要不要改， 由分诊这份打包材料或这条 issue 的人决定。
核心原则： 每条发现都要引用 path:line。没有引用，就不算发现。每个数字都来自
会话记录或你亲自跑过的命令，绝不凭记忆。
工作流
每一步建一个待办。第 5–7 步只在各自注明的条件下执行。
- 问题受理。 一次只问一个问题，直到你能写出一段陈述：点名是哪个（些）会话、 已知的话给出轮次范围、你的伙伴期望什么、实际发生了什么、他们关心的可观测量 （耗时、token、重复动作、某一个具体动作）。"太慢了"是抱怨，不是问题陈述。 记下目标是否是一份 superpowers bug 报告。
- 定位。 按
references/session-discovery.md把每个会话解析成经过核实的 绝对文件系统路径。确认过往会话时，引用它的第一条提示词和时间戳，并列出你排除的 每个候选及理由，没有就写"none"。枚举子智能体的会话记录。创建~/.superpowers/diagnosing-superpowers/<session-id>/，把路径告诉你的伙伴， 在其中填写templates/case.md，环境与技能观察遵循其中的来源标注规则。 - 分诊。 先亲自读报告问题附近的那一段。然后为每个维度并行派发一个分析员子智能体，
每个都给它：案例文件路径、
prompts/analyst-common.md，以及prompts/下的一个 维度文件：skill-timeline.md、plan-adherence.md、repeated-work.md、stumbles.md、quality-evidence.md、request-conflicts.md、cost-and-time.md。 会话记录很长时，按轮次范围拆分一个维度。凡是返回的发现没有path:line，一律丢弃。 - 报告。 按顺序填写
templates/report.md的每一节，写入工作区，展示出来， 并给出路径。核对被引用的内容实际能证明什么，并保留支撑它的案例；符号链接别名 不算冗余副本。 - GitHub issue —— 当报告 §7 写的是 possible 或 likely，或你的伙伴要求时。
按
references/github-issues.md在已开放和已关闭的 issue 中搜索这些症状。 展示匹配结果，建议把报告补充到最接近的那条。如果都不匹配，填写templates/issue.md，写入工作区，展示确切文本，获得批准后才创建 issue。gh不能附加文件；如果有打包材料，把路径给你的伙伴，让他们在浏览器里附上。 - 导出 —— 只在你的伙伴要求打包时进行；绝不主动打包。如果受理时的目标是 bug
报告，说一次"可以按需提供脱敏后的打包材料"，然后等待。询问脱敏级别，并说明每一级
包含什么：skeleton（不含工具结果正文）、evidence（只含被引用事件的正文）、full。
按
templates/bundle-README.md构建打包材料，派发prompts/scrub.md，再派发prompts/scrub-audit.md，两者反复执行，直到审计返回 CLEAN。 先完成打包模板里的证据核对与对账，再展示最终的脱敏日志、文件清单，以及隐私与 证据两方面的结论。获得批准后才归档（zip -r或tar -czf）。给出归档路径时， 说明其中包含什么，指向脱敏日志查看替换情况，并说明脱敏可能有遗漏：他们必须在 分享前逐个审阅每个文件。 - 相似会话 —— 被要求时进行。把已确认的发现转成一个特征签名，按修改时间和大小
列出候选，找到标记所在的行号，对每个候选并行派发
prompts/similar-session.md， 然后追加到报告 §9。
速查
七个分析员始终全部运行。这张表说明第 3 步里你自己先读哪一段，以及结论中先讲哪些发现。
| 抱怨 | 先读、先讲 |
|---|---|
| "太慢了" | cost-and-time、stumbles |
| "它为什么做了额外的活？" | repeated-work、plan-adherence |
| "为什么这么贵？" | cost-and-time |
| "它到底在干什么？"（仍在运行） | skill-timeline；在覆盖说明中注明仍在进行 |
| "它无视了计划" | plan-adherence，先看压缩（compaction）所在行 |
| "技能 X 从没触发" | skill-timeline |
What ships with it
19 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.
- prompts/analyst-common.md 1.6 KB
- prompts/cost-and-time.md 1.6 KB
- prompts/plan-adherence.md 1.7 KB
- prompts/quality-evidence.md 1.5 KB
- prompts/repeated-work.md 1.4 KB
- prompts/request-conflicts.md 974 B
- prompts/scrub-audit.md 1.3 KB
- prompts/scrub.md 1.4 KB
- prompts/similar-session.md 1.7 KB
- prompts/skill-timeline.md 1.6 KB
- prompts/stumbles.md 1.3 KB
- references/context-safety.md 979 B
- references/github-issues.md 1.8 KB
- references/redaction-policy.md 2.1 KB
- references/session-discovery.md 1.6 KB
- templates/bundle-README.md 3.5 KB
- templates/case.md 2.9 KB
- templates/issue.md 1.8 KB
- templates/report.md 2.4 KB
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.
- 18d ago First seen · 103 lines · 111 tokens per session scan A 6af901dddfcc
diagnosing-superpowers is a skill published in the GitHub repository jnMetaCode/superpowers-zh (8,335 stars, last pushed yesterday), licensed MIT. It adds 111 tokens to every session and 2,007 once invoked, about $0.0004 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-09-29.
Other skills, from other repositories
systematic-debugging
A step-by-step debugging guide for finding the real cause of software bugs before changing code.
concurrency-safety
A set of rules for writing safe concurrent and asynchronous code, where multiple tasks may run at the same time. It covers shared state, race conditions, deadlocks, timeouts, cancellation, and resource cleanup.
error-handling
A set of rules for handling errors and exceptions in software that performs file, network, database, or external-service operations.
performance-profiling
A guide for improving software speed by measuring where time and resources are actually being used before changing code.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.