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 agentmods add skills/re-cinq/wave/speckitnpx skills add re-cinq/wave --skill speckitgit clone --depth 1 https://github.com/re-cinq/waveWhat 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 | $0.00023 | $0.00627 |
| Opus 5 | $0.00012 | $0.00313 |
| Sonnet 5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
speckit 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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit - Specification-Driven Development Tools
SpecKit provides a comprehensive workflow for specification-driven development, from initial feature description to implementation planning.
Overview
SpecKit follows a structured workflow:
- Specify - Create feature specifications from natural language
- Clarify - Identify and resolve underspecified areas
- Plan - Generate implementation plans and design artifacts
- Validate - Analyze specifications for consistency and quality
- Implement - Execute implementation plans with task tracking
Available Commands
Core Workflow
| Command | Purpose | Usage |
|---|---|---|
speckit.specify |
Create or update feature specification | /speckit.specify "feature description" |
speckit.clarify |
Identify underspecified areas and ask clarification questions | /speckit.clarify |
speckit.plan |
Generate implementation plans and design artifacts | /speckit.plan |
speckit.implement |
Execute implementation plan with task tracking | /speckit.implement |
Analysis & Validation
| Command | Purpose | Usage |
|---|---|---|
speckit.analyze |
Cross-artifact consistency and quality analysis | /speckit.analyze |
speckit.tasks |
Generate actionable, dependency-ordered task list | /speckit.tasks |
speckit.checklist |
Generate custom validation checklist | /speckit.checklist |
Project Setup
| Command | Purpose | Usage |
|---|---|---|
speckit.constitution |
Create or update project constitution and principles | /speckit.constitution |
Standard Feature Development
/speckit.specify "Add user authentication system"
/speckit.clarify # if needed
/speckit.plan
/speckit.tasks
/speckit.implement
File Structure
specs/
├── [number]-[feature-name]/
│ ├── spec.md # Main specification
│ ├── plan.md # Implementation plan
│ ├── tasks.md # Task breakdown
│ └── checklists/
│ └── custom.md # Custom validation checklist
└── constitution.md # Project constitution
What ships with it
1 file 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.
- 2d ago First seen · 77 lines · 23 tokens per session scan A d28780a2f2cf
speckit is a skill published in the GitHub repository re-cinq/wave (20 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 627 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 skills, from other repositories
coordinate-agents
Route Codex-native multi-agent orchestration in a Git repository through a local-first, recoverable Agent Bus. Use for role-based planning, task execution, review, recovery, adapters, and human-gated release workflows. The plugin supports Codex CLI, Google Antigravity CLI, Claude, and other configured coding agents.…
coordinate-task
Run a Coordinate Agents Task from requirement clarification through planning, implementation, review, and the human release gate. Hide Agent Bus transport details behind the durable Task API.
coordinate-recover
Diagnose and safely resume Coordinate Agents Tasks after executable failure, non-zero exit, timeout, stale claim, processing message, or Implementer ERROR. Recovery is explicit and never an automatic retry loop.
coordinate-setup
Discover coding CLIs on the current computer and configure a Coordinate Agents implementation agent. Use for setup, executable checks, registered agents, user-level configuration, and project-over-user precedence.
coordinate-review
Review a Coordinate Agents implementation as the Codex Reviewer. Verify the real commit, diff, tests, validation evidence, and specification without modifying the Implementer's product code.
api-contracts
Enforce API contract governance, strict backward compatibility, schema validation, and standardized RFC 7807 error responses.