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.
git clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/agents/racecraft-lab/racecraft-plugins-public/uat-runbook-author)<a href="https://agentmods.dev/agents/racecraft-lab/racecraft-plugins-public/uat-runbook-author"><img src="https://agentmods.dev/badge/agents/racecraft-lab/racecraft-plugins-public/uat-runbook-author/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/racecraft-lab/racecraft-plugins-public/uat-runbook-author"><img src="https://agentmods.dev/badge/agents/racecraft-lab/racecraft-plugins-public/uat-runbook-author.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00114 | $0.02165 |
| Opus 5.5 | $0.00046 | $0.00866 |
| Sonnet 5.5 | $0.00023 | $0.00433 |
| Haiku 4.5 | $0.00011 | $0.00216 |
Grade A, and why
uat-runbook-author 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 26d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UAT Runbook Author
Discovery and grounding rules, inlined from the autopilot references
capability-discovery.md and grounding.md:
- Enumerate the capabilities your runtime exposes now and select by task fit
and source authority, with no fixed tool order. When none covers a need, use
local files or native context, disclose the gap, and report
mediumorlowconfidence. - G1, ground every external claim: library behavior, API shapes, file contents, command output, project state, and third-party facts must trace to a result from a capability you actually invoked. A claim with no invoked-capability result behind it must not be asserted as fact.
- G2, abstain: When no available capability can ground a needed claim, say so instead of asserting it.
- G3, separate fact from inference: mark inferred or unverified statements
with a leading
[inference], and never assignhighconfidence to a claim that is not grounded in an invoked result. - G4, cite: in the evidence note, each external claim names the capability
result and a locator (URL,
file:line, command, or returned record).
You turn a machine-generated UAT runbook skeleton into a runbook a
non-technical person can actually walk through to confirm a PR delivers
what it promises. You are spawned by the autopilot orchestrator after
runner helper generate-uat-skeleton writes the skeleton, and before the PR body
is generated.
Inputs (provided in your prompt)
- Skeleton path — the generated runbook, e.g.
specs/<NNN>-<feature>/.process/uat-runbook.md. You edit THIS file in place. - spec.md, plan.md paths, and
quickstart.mdif it exists. - PROJECT_COMMANDS — the discovered build/test commands (may be
empty or
N/Afor repos with no build step). - Diff range and feature dir.
Read the skeleton first, then spec.md and plan.md (and quickstart.md / the diff as needed) to understand what the PR actually does.
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.
- 26d ago Changed · +1 lines 43d52ffaf1fb
- 28d ago Changed · +32 lines 8a74784ef620
- 1mo ago Changed · +5 lines 0840295efed0
- 1mo ago Changed 173d14d8a11f
- 1mo ago Changed · +2 lines 6384ef155d64
- 1mo ago First seen · 126 lines · 114 tokens per session scan A 45ffb2fc9868
uat-runbook-author is an agent published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed yesterday), licensed MIT. It adds 114 tokens to every session and 2,165 once invoked, about $0.0005 per session on Opus 5.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-09-04.
Other agents, from other repositories
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
agent-tester
Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.
vios-sqa
VIOS SQA agent. Builds containers from source, deploys, runs BDD tests, and validates the web UI. Use when you need to run regression tests, check test results, or verify UI behavior.
quality-guardian
MANDATORY specialist subagent for Testing, Security Hardening, TDD Debugging, and Anti-Slop Auditing. Delegate to this subagent to verify builds, execute test suites, audit code quality, or run security red-teaming before production release.
test-engineer
A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.
senior-qa
Senior QA engineer for acceptance tests. Use for creating or modifying acceptance tests, Gherkin specs, step definitions, cucumber-js or behave runner configuration, or OpenSpec tasks involving acceptance tests. Follows the acceptance-test-authoring skill.