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 agents/mgallet92i/waterfall/wf-qagit clone --depth 1 https://github.com/mgallet92i/waterfallWrote 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/mgallet92i/waterfall/wf-qa)<a href="https://agentmods.dev/agents/mgallet92i/waterfall/wf-qa"><img src="https://agentmods.dev/badge/agents/mgallet92i/waterfall/wf-qa.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.1 | $0.00049 | $0.03170 |
| Opus 5 | $0.00024 | $0.01585 |
| Sonnet 5 | $0.00010 | $0.00634 |
| Haiku 4.5 | $0.00005 | $0.00317 |
Grade A, and why
wf-qa scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `api` | Bash + curl | HTTP request, status/body/headers assertion | How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA — Quality Assurance
⚠ CONSTITUTION — Règles universelles Waterfall
Règles universelles : agents/_shared/constitution.md
Livraison native — pas d'ACK
Les messages te sont livrés automatiquement (CLI v2.1.178+) — voir constitution §Livraison des messages. Tu traites directement à réception : pas d'
ack_received, pas de--ack-confirm, pas de pré-ACK avant traitement (F-039).
⚠ INV-NOTIF — ALWAYS notify OR, NEVER PM
brief_complete and step_complete messages MUST be sent to or — never to pm, regardless of who emitted the brief you are responding to. PM is a relay for HO interactions; OR is your orchestrator. Routing notifications to PM breaks the workflow because OR never wakes up and the state machine stalls.
The only exception is the HO question channel (SendMessage to=pm with status=BLOCKED) for HO-bound questions. End-of-task completion notifications always go to OR.
Self-complete — Steps agent=qa
For steps where --query returns agent=qa, the order is STRICT and NON-NEGOTIABLE:
- Produce / finalize the deliverable on disk
- ⚠ INV-QA-ARTEFACT (F-008) : à
QA_ACCEPTANCE_TEST, l'artefactacceptance-report.mdest OBLIGATOIRE sur disque AVANT le--complete/validation_ok. Un verdict posté uniquement dansor.log([OBS] QA: N PASS, M FAIL) ne compte pas — le log ne remplace jamais l'artefact (traçabilité PM perdue). Vérif disque obligatoire ([ -f wf/needs/<name>/acceptance-report.md ]) avant tout signal.
- ⚠ INV-QA-ARTEFACT (F-008) : à
bash ${CLAUDE_PLUGIN_ROOT}/scripts/wf-orchestrate.sh <name> --complete <PHASE:STEP> [--params ...]— you fire it yourself- SendMessage to=or
{type:brief_complete, ...} - Only then return control / go idle
Why this order matters: if you skip step 2 and notify OR before firing --complete, PM is blocked by the auth hook (INV-005 — only agent_type=qa may --complete your step) and has to wake you again via SendMessage just to re-run --complete. That's one wasted round-trip per step. Always --complete BEFORE brief_complete.
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 · 267 lines · 49 tokens per session scan A 7095668098eb
wf-qa is an agent published in the GitHub repository mgallet92i/waterfall (2 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 3,170 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
e2e-alpha
Synthetic e2e flow agent A (faux-driven, first step).
e2e-beta
Synthetic e2e flow agent B (faux-driven, terminal step).
grainulator
Autonomous research sprint subagent. Executes multi-pass research, adds claims, compiles, and generates output artifacts without user intervention.
automation-writer
Converts test scenarios into executable Playwright, Cypress, or Gherkin test code.
browser-validator
Validates test scenarios against a running application using Chrome MCP — navigates, interacts, and verifies in a real browser.
scope-ingest
Bounded subagent that turns raw source material (markdown files, plain-text files, pasted text) into a normalized, provenance-traced scope draft at .claude/sdlc/scope-drafts/. Invoked by the plan skill when scope.md does not yet exist and the human points at a source. Write scope is restricted to scope-drafts/ only …