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/thierryn/fire-flow/fire-verify-uatgit clone --depth 1 https://github.com/ThierryN/fire-flowWrote 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/thierryn/fire-flow/fire-verify-uat)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-verify-uat"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-verify-uat.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.00011 | $0.00884 |
| Opus 5 | $0.00005 | $0.00442 |
| Sonnet 5 | $0.00002 | $0.00177 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
fire-verify-uat 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-verify-uat
Conversational UAT testing with automatic parallel diagnosis when flows fail.
Arguments
arguments:
phase:
required: false
type: string
description: "Phase to test (e.g., 03). Defaults to current phase."
Process
Step 1: Load Phase Context
+---------------------------------------------------------------+
| DOMINION FLOW >>> UAT VERIFICATION |
+---------------------------------------------------------------+
Read all RECORD.md files from the phase. Extract:
- What was built (from quick summaries)
- Critical flows (from PROJECT.md)
- Must-haves (from BLUEPRINT.md frontmatter)
Step 2: Generate Test Flows
Create test flows from must-haves truths:
Critical Flows to Test:
1. [Must-have truth 1] - Must Pass
2. [Must-have truth 2] - Must Pass
3. [Edge case from PROJECT.md] - Should Pass
Present to user: "Ready to start UAT? I'll guide you through each flow."
Step 3: Guided Testing
For each flow:
- Present exact steps to test
- Wait for user result (pass/fail/issue description)
- Record result
+---------------------------------------------------------------+
| TESTING: Flow 1 of N |
+---------------------------------------------------------------+
| |
| Flow: User can register with email and password |
| |
| Steps: |
| 1. Run: npm run dev |
| 2. Visit: http://localhost:3000/register |
| 3. Enter email: [email protected] |
| 4. Enter password: SecurePass123! |
| 5. Click "Register" |
| |
| Expected: Redirect to /dashboard, welcome message |
| |
|-----------------------------------------------------------------|
| Result? Type "pass", "fail", or describe the issue |
+-----------------------------------------------------------------+
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 · 147 lines · 11 tokens per session scan A c87cff0403d9
fire-verify-uat is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 23d ago), licensed MIT. It adds 11 tokens to every session and 884 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-09-03.
Other commands, from other repositories
e2e
Generate and run E2E tests with Playwright.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
e2e
使用 Playwright 生成并运行端到端 (E2E) 测试.
explore-release
Model tier: opus — Opus session for the orchestrator. Charter agents run as parallel general-purpose background Tasks; tier them by cost (sonnet is usually sufficient for a single charter's execution).