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 commands/gaia-react/gaia/constitution-checkgit clone --depth 1 https://github.com/gaia-react/gaiaWhat 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.00018 | $0.00661 |
| Opus 5 | $0.00009 | $0.00331 |
| Sonnet 5 | $0.00004 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
constitution-check 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constitution + version-pin precondition check
Fired automatically by spec-kit on the before_specify event (mandatory hook). The agent reads this skill and runs the two checks below before /speckit-specify proceeds.
Inputs
$ARGUMENTS: the same arguments the user passed to/speckit-specifyor/speckit-gaia-spec. Echoed through unchanged; this hook does not consume them.- Working directory, the project root (a spec-kit-initialized project containing
.specify/memory/constitution.mdand.specify/extensions/gaia/extension.yml).
Step 1: version-pin drift detection
Run the version-check helper using the Bash tool, and capture its result:
bash .specify/extensions/gaia/lib/version-check.sh
The helper reads requires.speckit_version from .specify/extensions/gaia/extension.yml, resolves the runtime spec-kit version, and exits 0 on match or non-zero on drift. On drift, surface the helper's stderr verbatim to the user, do not proceed, and announce:
before_specifyblocked: spec-kit version drift detected. Align versions before continuing, see message above.
Step 2: constitution placeholder scan
Read .specify/memory/constitution.md. Match the bracketed-placeholder pattern \[[A-Z_0-9]+\] (e.g. [PROJECT_NAME], [PRINCIPLE_1_NAME], [CONSTITUTION_VERSION]). If any matches are present:
-
Report the count and the first three placeholder identifiers found.
-
Block proceed with the message:
before_specifyblocked: spec-kit constitution still contains placeholder values. Run/speckit-constitutionto populate it before authoring a SPEC. -
Do not proceed to
/speckit-specify.
If the file is absent entirely, treat as the same block (constitution must exist).
Step 3: pass-through
If both checks pass, emit a single confirmation line and let /speckit-specify continue:
before_specifyok: constitution populated, spec-kit version matches pin.
This hook has no return value to spec-kit. After emitting the confirmation line, return control to the caller, end this hook's turn and let the running /speckit-specify (or /speckit-gaia-spec) skill continue. Do not call any further tool on the pass-through path.
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 · 52 lines · 18 tokens per session scan A 4d33b9e04cc6
constitution-check is a command published in the GitHub repository gaia-react/gaia (22 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 661 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
pr-description
Generate a pull request description based on the changes in the current branch.
push-changes
If no topic provided, just document the recent changes. If a topic is provided, focus on documenting that topic.
create-PR
Command "create-PR" from bartstc/vite-ts-react-template, covering create a pr against this branch: $arguments, follow these steps and remember.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.