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/wiki-promotegit 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/wiki-promote)<a href="https://agentmods.dev/commands/gaia-react/gaia/wiki-promote"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/wiki-promote.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.00023 | $0.05667 |
| Opus 5 | $0.00012 | $0.02833 |
| Sonnet 5 | $0.00005 | $0.01133 |
| Haiku 4.5 | $0.00002 | $0.00567 |
Grade A, and why
speckit-gaia-wiki-promote 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 5d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Promote, after_implement hook
Fires automatically on /speckit-implement completion for the spec arm (SPEC-NNN); also invokable directly with a PLAN-NNN id for the plan arm (from plan-close, on an accepted promotion offer). Reads the consolidated SUMMARY.md, detects whether the implementing PR has merged, and either promotes content into gaia/wiki/ or persists a defer flag.
Step 1 - Resolve the source
The hook fires on /speckit-implement completion for the spec arm. The agent has the SPEC ID in conversation context (the implementer agent referenced it). For the plan arm, the caller (plan-close) passes the PLAN-NNN id directly as the invocation argument.
Identify the id from the running conversation or invocation argument. If ambiguous on the spec arm, fall back to the most-recently-modified .gaia/local/specs/SPEC-*/SUMMARY.md (or SPEC.md under the legacy fallback below), deriving the SPEC ID from the parent folder name (excluding -revised-contracts and -refit-decision suffixes).
Resolve the source path by id shape:
SPEC-NNN→.gaia/local/specs/SPEC-NNN/SUMMARY.mdPLAN-NNN→.gaia/local/plans/PLAN-NNN/SUMMARY.md
Read the consolidated SUMMARY.md frontmatter. Required fields: wiki_promote_default, wiki_promote_targets (may be an empty list).
Legacy fallback (pre-consolidation SPECs): if SUMMARY.md is absent but a legacy SPEC.md still exists in the same folder, fall back to reading SPEC.md's frontmatter and body instead; downstream steps (title, body, routing) source from whichever file resolved here.
If neither SUMMARY.md nor a legacy SPEC.md exists, exit with: wiki-promote: no consolidated SUMMARY.md or SPEC artifact found; nothing to promote.
Step 2 - Read promotion gate
Branch on wiki_promote_default:
no→ exit silently with:wiki-promote: SPEC-NNN skipped per frontmatter (wiki_promote_default: no).ask→ surfaceAskUserQuestion:- Question:
Promote SPEC-NNN to wiki? (default yes) - Options:
Yes, promote now/No, skip silently/Preview pages without writing - On
Yes→ continue to Step 3. - On
No→ exit silently with the skip report. - On
Preview→ render the candidate pages (call Step 4 + Step 5 in dry-run mode), print to stdout, exit without writing. Mark this branch with--previewfor downstream tasks.
- Question:
yes→ continue to Step 3.- Any other value → emit warning
wiki-promote: unrecognized wiki_promote_default '<value>'; treating as 'no'.and exit silently.
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.
- 5d ago First seen · 342 lines · 23 tokens per session scan A a1ec5a81ed05
speckit-gaia-wiki-promote is a command published in the GitHub repository gaia-react/gaia (23 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 5,667 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.
replan-remaining-work
Command "replan-remaining-work" from udecode/plate, covering command: re-plan remaining work, when to run, hard rule, invocation and refresh afterward.
review-arch
Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.
a11y-audit-react
Identify accessibility violations in React components and provide actionable remediation aligned with WCAG 2.2 Level AA. This is the guided audit workflow that applies the standards defined in the a11y-automation and react-components rules.
react-build
Fix React build failures (Vite, webpack, Next.js, CRA, Parcel, esbuild, Bun) incrementally — JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types. Invokes the react-build-resolver agent for minimal, surgical fixes.
next-upgrade
Structured workflow for upgrading Next.js applications across major versions. Use when migrating a Next.js project from one major version to another (e.g., 13 to 14, 14 to 15, 15 to 16). Covers codemod automation, breaking change detection, incremental migration paths, and post-upgrade validation.