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.spec-kit)<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex.spec-kit"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex.spec-kit/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/commands/rhuss/cc-spex/speckit.spex.spec-kit"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex.spec-kit.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.00007 | $0.02683 |
| Opus 5 | $0.00003 | $0.01341 |
| Sonnet 5 | $0.00001 | $0.00537 |
| Haiku 4.5 | $0.00001 | $0.00268 |
Grade A, and why
speckit.spex.spec-kit 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Kit Technical Integration
CRITICAL NAMING - READ THIS FIRST
| What | Correct Name | WRONG Names |
|---|---|---|
| CLI command | specify |
|
| Package name | specify-cli |
|
| Slash commands | /speckit-* |
(these are correct) |
Installation: uv pip install specify-cli or pip install specify-cli
Purpose
This skill is the single source of truth for all spec-kit technical integration:
- Automatic initialization and setup
- Installation validation
- Project structure management
- Slash command availability
- Layout and file path enforcement
This is a low-level technical skill. Workflow skills (brainstorm, implement, etc.) call this skill for setup, then proceed with their specific workflows.
CRITICAL: Understanding the Tool Architecture
The specify CLI is a setup tool only. It has three commands:
specify init- Initialize a project with spec-kit templates and commandsspecify check- Check that required tools are installedspecify version- Display version information
All spec operations are done via /speckit-* slash commands, which are installed by specify init:
/speckit-specify- Create specifications/speckit-plan- Generate implementation plans/speckit-tasks- Generate task lists/speckit-clarify- Find underspecified areas/speckit-analyze- Cross-artifact consistency check/speckit-checklist- Generate quality checklists/speckit-implement- Execute implementation/speckit-constitution- Create project constitution
NEVER call specify validate, specify plan, etc. - these commands don't exist!
Automatic Initialization
IMPORTANT: This runs automatically when called by any workflow skill.
Check <spex-initialized> in the <spex-context> system reminder:
- If
true: Skip initialization entirely. The project is already set up. - If
falseor missing: Run/spex:initto initialize. If init prompts for restart, pause this workflow and resume after restart.
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 · 367 lines · 7 tokens per session scan A 153b2ac1d8c4
speckit.spex.spec-kit is a command published in the GitHub repository rhuss/cc-spex (116 stars, last pushed 21d ago), licensed Apache-2.0. It adds 7 tokens to every session and 2,683 once invoked, about $0.0000 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.