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.
git clone --depth 1 https://github.com/rhuss/cc-spexWrote 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/commands/rhuss/cc-spex/speckit.spex.using-superpowers)<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex.using-superpowers"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex.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.00019 | $0.03167 |
| Opus 5 | $0.00010 | $0.01584 |
| Sonnet 5 | $0.00004 | $0.00633 |
| Haiku 4.5 | $0.00002 | $0.00317 |
Grade A, and why
speckit.spex.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 7d 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 — 346 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. This is not optional. You cannot rationalize your way out of this.
Getting Started with spex
What is spex?
SDD = Specification-Driven Development. spex is the Claude Code plugin that implements it.
SDD is a development methodology where specifications are the single source of truth:
- Specs created before code
- Code validated against specs
- Specs evolve with implementation reality
- Quality gates enforce spec compliance
This plugin combines two upstream projects:
- Superpowers (by Jesse Vincent): Process discipline, TDD enforcement, verification gates, anti-rationalization patterns, and foundational skills (debugging, git worktrees, parallel agents)
- Spec-Kit (by GitHub): Specification templates, artifact management, and the
specifyCLI
spex extends these with spec-first enforcement, compliance scoring, drift detection, and evolution. Several upstream superpowers skills are modified with spec-awareness (verification, code review, brainstorming, plan review), while others are used unchanged.
Technical Prerequisites
All technical setup is handled by /spex:init. Spec-kit and extensions must be initialized before using any workflow command. If .specify/ directory does not exist, tell the user to run /spex:init first. Do not check for or search for any CLI tools. Focus on choosing the right workflow.
MANDATORY FIRST RESPONSE PROTOCOL
Before responding to ANY user message, you MUST complete this checklist:
- List available spex skills in your mind
- Ask yourself: "Does ANY spex skill match this request?"
- If yes -> Use the Skill tool to read and run the skill file
- Announce which skill you're using
- Follow the skill exactly
Responding WITHOUT completing this checklist = automatic failure.
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.
- 7d ago First seen · 346 lines · 19 tokens per session scan A 0d259acf78f6
speckit.spex.using-superpowers is a command published in the GitHub repository rhuss/cc-spex (115 stars, last pushed 18d ago), licensed Apache-2.0. It adds 19 tokens to every session and 3,167 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.