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/mgallet92i/waterfall/quitgit 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/commands/mgallet92i/waterfall/quit)<a href="https://agentmods.dev/commands/mgallet92i/waterfall/quit"><img src="https://agentmods.dev/badge/commands/mgallet92i/waterfall/quit.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.00004 | $0.00238 |
| Opus 5 | $0.00002 | $0.00119 |
| Sonnet 5 | $0.00001 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
waterfall:quit 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 4d 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.
What it actually says
Cleanly stops the active workflow (shutdown teammates, marker cleanup, state preservation).
Argument: none. The active session is detected automatically via ~/.claude/wf-session-active.<session_id>.
What this command does
- Loads the
wf-quitskill viaSkill - The skill detects the active session (
wf-session-active.<sid>) - Sends
shutdown_requestto each active teammate of the team - Calls
scripts/wf-quit.sh --session-id <sid>to clean up markers - Displays confirmation +
/waterfall:resume <need>command to resume
Entry procedure
Skill({name: "wf-quit", args: "$ARGUMENTS"})
Guarantees
.wf-state.jsonis never modified — the need's state is fully preserved- Idempotent: if no workflow is active, neutral message without error
- Resume available immediately via
/waterfall:resume <need>
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.
- 4d ago First seen · 30 lines · 4 tokens per session scan A 248e4fa99464
waterfall:quit is a command published in the GitHub repository mgallet92i/waterfall (2 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 238 once invoked, about $0.0000 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-31.
Other commands, from other repositories
token-review
Analyze SDLC token usage from .claude/sdlc/token-log.json (last run) and token-history.jsonl (rolling). Surfaces the biggest cost centers and concrete optimization candidates. Read-only.
start
Activate the SDLC workflow (opt-in), re-enable after suspension, or start a new task when already enabled. On fresh install — auto-detects repo/CI/stack/tracker (≤3 prompts), creates .enabled, takes a one-sentence task description, and auto-generates scope.md and a draft plan. On re-enable — verifies the suspension…
build
Start Phase 4 — implement the approved design with surgical-edit discipline and work-item traceability.
configure
Guided setup for config/tools.json and config/tools.local.json. Replaces manual file editing for first-time setup and common reconfigurations. Auto-invoked on fresh install (Layer 0) and when a command finds its required config missing (Layer 2). Safe to run anytime for proactive changes.
design
Start Phase 3 — produce or update application / data / platform / infrastructure / security / test architecture, technical specs, and test cases.
fix-fast
Compressed SDLC path for small bug fixes only — collapses Plan + Analyze + Design into a single mini-gate. Not for new builds or change requests.