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/specgit 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.00030 | $0.00417 |
| Opus 5 | $0.00015 | $0.00209 |
| Sonnet 5 | $0.00006 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
spec 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.
What it actually says
/speckit-gaia-spec, thin redirect to the GAIA router
This command exists because spec-kit's extension manifest schema requires provides.commands[] to be non-empty, and because the three GAIA hook targets (speckit.gaia.constitution-check, speckit.gaia.lint, speckit.gaia.self-review) need an extension to anchor them to. The canonical user-facing entry point for the GAIA Socratic discovery flow is /gaia-spec, which lives alongside /gaia-plan, /gaia-handoff, /gaia-pickup, and /gaia-audit as the GAIA workflows.
Dispatch
Read .claude/skills/gaia/references/spec.md and follow it, treating $ARGUMENTS as the feature description.
That reference is the single source of truth for the orchestration: pre-flight, /speckit-specify, gate 1, GAIA's Socratic clarify loop, the self-review, gate 2, the after_specify lint, save, and the /gaia-plan handoff prompt.
Why this is one line
Two doors into the same orchestrator:
| Door | Layer | Body |
|---|---|---|
/gaia-spec |
Command (.claude/commands/gaia-spec.md) |
Reads $ARGUMENTS, dispatches to references/spec.md. |
/speckit-gaia-spec |
Auto-generated by specify extension add |
This file. One-line redirect to the same references/spec.md. |
Never duplicate orchestration logic into this file. The drift cost between two parallel orchestrators outweighs the convenience. One source of truth (references/spec.md); two doors into it.
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 · 25 lines · 30 tokens per session scan A 84fdab70714c
spec is a command published in the GitHub repository gaia-react/gaia (22 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 417 once invoked, about $0.0002 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.
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
release-note-csoar
Automates the creation of Cloud SOAR (Automation Service) release notes for platform updates, integration changes, and bug fixes.
doc
Use this command to create a new feature doc, how-to, concept, reference, or troubleshooting guide — it scaffolds the file, frontmatter, structure, and sidebar entry.