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.extensions)<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex.extensions"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex.extensions.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.00013 | $0.00440 |
| Opus 5 | $0.00006 | $0.00220 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
speckit.spex.extensions 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.
What it actually says
Spex Extensions Management
Manage which spex extensions are active. Extensions provide additional capabilities such as quality gates, team orchestration, worktree isolation, and deep review.
Available extensions: spex-gates, spex-deep-review, spex-teams, spex-worktrees
Parse Arguments
Parse $ARGUMENTS for the subcommand and optional extension name:
- No arguments or
list-> List enable <extension-name>-> Enabledisable <extension-name>-> Disable
Subcommand: List (default)
Run via Bash:
specify extension list
Display the output to the user.
Subcommand: Enable
Run via Bash:
specify extension enable <extension-name>
Report the result to the user.
Subcommand: Disable
- Run
specify extension listand check if the extension is already disabled. If so, report that and STOP. - Warn the user: Disabling an extension requires regenerating all spec-kit files, which resets any manual customizations to
.claude/skills/speckit-*/SKILL.mdand.specify/templates/*.mdfiles. - Present options to the user to confirm:
- Question: "Disabling an extension will reset all spec-kit files to defaults (losing any manual customizations). Proceed?"
- Header: "Confirm"
- Options:
- Label: "Yes, disable", Description: "Reset spec-kit files and remove this extension's overlays"
- Label: "Cancel", Description: "Keep current extension configuration unchanged"
- If cancelled: report "Extension disable cancelled." and STOP.
- If confirmed, run these commands sequentially via Bash:
specify extension disable <extension-name> specify init --here --ai claude --force specify extension apply - Report which extensions are still active.
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 · 59 lines · 13 tokens per session scan A dd3cbe8c6c8d
speckit.spex.extensions is a command published in the GitHub repository rhuss/cc-spex (115 stars, last pushed 18d ago), licensed Apache-2.0. It adds 13 tokens to every session and 440 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.