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 superpowers-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/superpowers-openspec-superpowers-workflow)<a href="https://agentmods.dev/skills/syz-coder/superpowers-openspec-team-skills/superpowers-openspec-superpowers-workflow"><img src="https://agentmods.dev/badge/skills/syz-coder/superpowers-openspec-team-skills/superpowers-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/superpowers-openspec-superpowers-workflow"><img src="https://agentmods.dev/badge/skills/syz-coder/superpowers-openspec-team-skills/superpowers-openspec-superpowers-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.01673 |
| Opus 5 | $0.00020 | $0.00837 |
| Sonnet 5 | $0.00008 | $0.00335 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade A, and why
superpowers-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 9d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superpowers -> OpenSpec -> Superpowers Workflow
Overview
Use this skill when the team wants a delivery path that feels calm, deliberate, and hard to derail:
- Explore with Superpowers
- Lock the change with OpenSpec
- Return to Superpowers for implementation, testing, and verification
- Archive the completed OpenSpec change
This skill is an orchestrator. It should delegate detail work to the existing workflow skills instead of duplicating them.
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, read PROJECT_CONTEXT.md, CURRENT_STATE.md, DECISIONS.md, KNOWN_FAILURES.md, VERIFICATION_BASELINE.md, TEAM_PREFERENCES.md, USER_PROFILE.md, AGENT_NOTES.md, and the newest session journal entries at the start, then update the relevant files before final archive so the next session can resume with real context.
Required Order
- Start with
$superpowers-feature-workflow. Use it to clarify scope, compare approaches, confirm the solution shape, and capture the design draft. - Move to
$openspec-feature-workflow. Use it to create the change and completeproposal.md,design.md,specs/.../spec.md, andtasks.md. - 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. Acceptcontinue-devas the primary continuation command. - Do not route the confirmed task handoff through OpenSpec apply.
- If the user chooses execution development, return to
$superpowers-feature-workflow. Use it to write the implementation plan, prefer a worktree, execute with TDD, and run fresh verification. - After execution development completes, pause again and ask whether to continue code review.
Accept
continue-reviewas the primary continuation command. - If implementation and specs are aligned after verification, use
$openspec-archive-changeto archive the completed change. Before that final step, you may pause and ask whether to continue archive. Acceptcontinue-archiveas the primary continuation command, or continue to use$openspec-archive-change. - If
.superpowers-memory/exists, perform a memory alignment check after verification and archive decisions: ensure durable facts, current state, decisions, failure patterns, and session outcome are reflected in the right files. - Prefer
scripts/run-superpowers-memory-closeout.ps1when you want one command to review the checklist, get update suggestions, and optionally run validation after execution or archive work. - Use
scripts/suggest-superpowers-memory-updates.ps1if it is still unclear which memory surfaces should be updated after implementation, verification, or archive work. - When memory quality matters for the project, run
scripts/validate-superpowers-memory.ps1before the final completion claim.
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.
- 9d ago First seen · 102 lines · 40 tokens per session scan A 1665e9ef8899
superpowers-openspec-superpowers-workflow is a skill published in the GitHub repository SYZ-Coder/superpowers-openspec-team-skills (192 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,673 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…