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/uat-writegit 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.00032 | $0.01140 |
| Opus 5 | $0.00016 | $0.00570 |
| Sonnet 5 | $0.00006 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
uat-write 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UAT auto-write pass
Fired automatically by spec-kit on the before_implement event (mandatory hook). The agent reads this skill and renders the active SPEC's PO-authored UATs into one Playwright e2e spec per UAT, leaving a red-state harness in place before /speckit-implement edits source.
Locate the active SPEC
The render target is the SPEC artifact whose UATs back the upcoming /speckit-implement run. In a GAIA project that artifact lives at .gaia/local/specs/SPEC-NNN/SPEC.md.
Resolve the path in this order (4-step algorithm; locked post-probe, .specify/feature.json carries no SPEC backreference, so a feature-cross-walk step was dropped):
- If
$ARGUMENTScarries an explicitSPEC-NNNid or absolute path, use it. - Otherwise pick the most-recent
.gaia/local/specs/SPEC-NNN/SPEC.mdwithstatus: in-progress, modified within the last 30 minutes. - Otherwise the single
.gaia/local/specs/SPEC-NNN/SPEC.mdwithstatus: in-progress(only if exactly one exists). - Otherwise
AskUserQuestion: list all in-progress SPECs and ask which one to render. Do NOT guess.
The GAIA preset's /speckit-specify wrapper relocates and stamps the SPEC immediately after authoring, so the just-written SPEC is the most-recent in-progress entry, step 2 covers the /speckit-specify → /gaia-plan → /speckit-implement chain. Step 3 handles the common single-feature case.
Run the render helper
Run using the Bash tool:
bash .specify/extensions/gaia/lib/uat-write.sh <resolved-spec-path>
The helper emits a JSON summary on stdout. Capture it verbatim; do NOT pipe through anything else. Exit codes: 0 success, 1 operational failure, 2 usage error.
Surface results
-
Success (
ok: true). Emit a one-line summary:before_implementUAT-write complete: written, rewritten, deleted, fixme, unchanged. Specs at.playwright/e2e/<spec-dir>/. Cache:.gaia/local/cache/uat-write/<SPEC-ID>.json.
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 · 58 lines · 32 tokens per session scan A 09263f91d5a1
uat-write is a command published in the GitHub repository gaia-react/gaia (22 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 1,140 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.
favicon-gen
Generate a favicon package from a logo or brand.
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.
build
Build the Band Play Chrome extension into dist/ (webpack.prod.js).
review-extension
Browser-extension + bridge review with extension-reviewer (Primary Owner).