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/self-reviewgit clone --depth 1 https://github.com/gaia-react/gaiaWrote 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/gaia-react/gaia/self-review)<a href="https://agentmods.dev/commands/gaia-react/gaia/self-review"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/self-review.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.01112 |
| Opus 5 | $0.00010 | $0.00556 |
| Sonnet 5 | $0.00004 | $0.00222 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
self-review 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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-review pass before gate 2
The /gaia-spec wrapper dispatches this directly at step 6 as a general-purpose Agent, after the Socratic clarify loop and before the GAIA wrapper presents the rendered artifact for gate-2 confirmation. The extension also declares it on spec-kit's after_clarify event, so a bare /speckit-clarify invocation fires it too.
Inputs
- The in-progress SPEC draft. The wrapper writes the working draft to
.gaia/local/cache/draft.mdduring the loop; the path may also be supplied via$ARGUMENTS. - The gate-1 snapshot at
.gaia/local/cache/gate1-<spec_id>.json, captured when the user confirmed intent + UATs.
Audit checklist
Read the draft and the gate-1 snapshot. Record every finding under the headings below (the spec.md 6a dispatch prompt is the authoritative return/apply contract): write them to .gaia/local/cache/audit-<spec_id>/findings/self-review.json, apply the low and medium suggested_fixes to the draft yourself in a single write, and surface the high findings to the wrapper for gating.
1. Placeholder text
Scan for [PLACEHOLDER], <TODO>, <TBD>, FIXME, and bare TBD tokens. Any hit is a finding: name the field and the offending line.
2. Scope drift relative to gate 1
Compare draft fields against the gate-1 snapshot:
intentparagraph diverged in shape, not just polish.- A UAT was renumbered, removed, or added since gate 1.
success_criteriagained or lost an entry without a corresponding answered clarification.
For each drift, name the gate-1 value, the current value, and ask the wrapper to surface a confirmation prompt before gate 2 (or to revert).
3. Internal inconsistency
Cross-check fields against each other:
- A UAT references a behavior absent from
intentorsuccess_criteria. scope_boundaries.alwaysincludes a behavior contradicted byscope_boundaries.never.clarifications.answered[]entries that contradict the currentintent.
4. Ambiguous UAT phrasing
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.
- 4d ago First seen · 90 lines · 19 tokens per session scan A 81c284a0b3d2
self-review is a command published in the GitHub repository gaia-react/gaia (23 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,112 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
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
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.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
vite-react-setup
Setup project React SPA mới với Vite + TypeScript + Tailwind CSS v3 + Vitest. Dùng khi bắt đầu dự án frontend mới, cần scaffold đầy đủ config, brand KZTEK colors, và test setup sẵn sàng.
scaffold-react
Quickly scaffold a new React + TypeScript project with Claude Code configuration.
create-form
Create a comprehensive form with React Hook Form, Zod validation, error handling, and loading states.