Borrowing it
Nothing to install: this file belongs to re-cinq/wave. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/re-cinq/wave/main/.claude/skills/speckit/SKILL.mdgit clone --depth 1 https://github.com/re-cinq/waveWrote 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/re-cinq/wave/speckit)<a href="https://agentmods.dev/skills/re-cinq/wave/speckit"><img src="https://agentmods.dev/badge/skills/re-cinq/wave/speckit/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/re-cinq/wave/speckit"><img src="https://agentmods.dev/badge/skills/re-cinq/wave/speckit.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.00023 | $0.00627 |
| Opus 5.5 | $0.00009 | $0.00251 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 77 lines · 23 tokens per session scan A d28780a2f2cf
speckit is a skill published in the GitHub repository re-cinq/wave (23 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 627 once invoked, about $0.0001 per session on Opus 5.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-task
Create, execute, inspect, or stop Coordinate Agents Tasks when requested, or continue an existing Coordinate Agents Task.
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 or configure implementation agents for Coordinate Agents when setting up or changing its agent configuration.
coordinate-agents
Route requests that explicitly use Coordinate Agents or operate on its existing Tasks to setup, execution, review, or recovery skills.
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.
backend
Backend development skill for microservices following Clean Architecture, CQRS with a transactional outbox, the repository/use-case pattern, and a Testing-Trophy strategy.