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 SYZ-Coder/superpowers-openspec-team-skills --skill openspec-superpowers-workflowgit clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skillsWrote 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/syz-coder/superpowers-openspec-team-skills/openspec-superpowers-workflow)<a href="https://agentmods.dev/skills/syz-coder/superpowers-openspec-team-skills/openspec-superpowers-workflow"><img src="https://agentmods.dev/badge/skills/syz-coder/superpowers-openspec-team-skills/openspec-superpowers-workflow/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/syz-coder/superpowers-openspec-team-skills/openspec-superpowers-workflow"><img src="https://agentmods.dev/badge/skills/syz-coder/superpowers-openspec-team-skills/openspec-superpowers-workflow.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.00059 | $0.01291 |
| Opus 5.5 | $0.00024 | $0.00516 |
| Sonnet 5.5 | $0.00012 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
openspec-superpowers-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec + Superpowers Workflow
Overview
Use this skill as the OpenSpec-first feature delivery entrypoint. It creates and validates OpenSpec change artifacts first, then hands the completed task checklist to Superpowers for implementation planning, TDD, and verification.
This is an explicit opt-in workflow. Do not use it by default. Only use it when the user explicitly asks for this workflow, names this skill, or a repository policy explicitly requires it.
If .superpowers-memory/ exists in the repository, treat it as shared project memory: read it before planning and update it before closing the workflow.
Required Order
- Run
$openspec-feature-workflowfirst. Use it to clarify the change enough to create and completeproposal,design,specs, andtasks. - Stop OpenSpec apply-style execution after
tasks.mdis complete. - Present the generated OpenSpec task checklist to the user.
- By default, wait for explicit confirmation before implementation planning starts.
- After the user confirms
tasks.md, pause once more and ask whether to continue execution development. Accept either继续开发orcontinue-devas the explicit continuation command. - Do not route the confirmed task handoff through OpenSpec apply.
- If the user chooses execution development, hand off to the Superpowers track for implementation planning, worktree setup, TDD, and verification.
- After execution development completes, pause again and ask whether to continue code review.
Accept either
继续审查orcontinue-reviewas the explicit continuation command. - If the project uses OpenSpec archive flow and code, specs, and verification are aligned, archive the change as the final OpenSpec step.
Before that final step, you may pause and ask whether to continue archive.
Accept either
继续归档orcontinue-archiveas the explicit continuation command, or continue to use$openspec-archive-change. - Do not claim completion until verification evidence exists.
- If
.superpowers-memory/exists, updateCURRENT_STATE.mdand add a short journal entry for the session outcome.
What ships with it
4 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 · 80 lines · 59 tokens per session scan A 26d8d91ed778
openspec-superpowers-workflow is a skill published in the GitHub repository SYZ-Coder/superpowers-openspec-team-skills (200 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 1,291 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…