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/commands/speckit.constitution.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/commands/re-cinq/wave/speckit.constitution)<a href="https://agentmods.dev/commands/re-cinq/wave/speckit.constitution"><img src="https://agentmods.dev/badge/commands/re-cinq/wave/speckit.constitution/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/re-cinq/wave/speckit.constitution"><img src="https://agentmods.dev/badge/commands/re-cinq/wave/speckit.constitution.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.00020 | $0.01042 |
| Opus 5.5 | $0.00008 | $0.00417 |
| Sonnet 5.5 | $0.00004 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
speckit.constitution 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.
This is a copy
95% identical to speckit.constitution — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
You are updating the project constitution at .specify/memory/constitution.md. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. [PROJECT_NAME], [PRINCIPLE_1_NAME]). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.
Follow this execution flow:
-
Load the existing constitution template at
.specify/memory/constitution.md.- Identify every placeholder token of the form
[ALL_CAPS_IDENTIFIER]. IMPORTANT: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
- Identify every placeholder token of the form
-
Collect/derive values for placeholders:
- If user input (conversation) supplies a value, use it.
- Otherwise infer from existing repo context (README, docs, prior constitution versions if embedded).
- For governance dates:
RATIFICATION_DATEis the original adoption date (if unknown ask or mark TODO),LAST_AMENDED_DATEis today if changes are made, otherwise keep previous. CONSTITUTION_VERSIONmust increment according to semantic versioning rules:- MAJOR: Backward incompatible governance/principle removals or redefinitions.
- MINOR: New principle/section added or materially expanded guidance.
- PATCH: Clarifications, wording, typo fixes, non-semantic refinements.
- If version bump type ambiguous, propose reasoning before finalizing.
-
Draft the updated constitution content:
- Replace every placeholder with concrete text (no bracketed tokens left except intentionally retained template slots that the project has chosen not to define yet—explicitly justify any left).
- Preserve heading hierarchy and comments can be removed once replaced unless they still add clarifying guidance.
- Ensure each Principle section: succinct name line, paragraph (or bullet list) capturing non‑negotiable rules, explicit rationale if not obvious.
- Ensure Governance section lists amendment procedure, versioning policy, and compliance review expectations.
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 · 79 lines · 20 tokens per session scan A e4abb5d0314d
speckit.constitution is a command published in the GitHub repository re-cinq/wave (23 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,042 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to speckit.constitution, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
deep-audit.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
bet
Lock a shaped Shape-Up pitch as a bet for the next cycle.
replay
sentry replay download writes a flat, time-ordered array of rrweb events, ready for rrweb-player or rrvideo. Sentry's custom events (breadcrumbs, performance spans) are kept.
gh-setup
Use to set up or update gh-workflow in a repository - analyzes tech stack, detects conventions, generates workflow configuration, and upgrades existing installations to latest version.
new-feature
Start a new feature — creates an Intent Document and begins the agent pipeline.
adr
Create an Architectural Decision Record (ADR) to document a significant technical decision.