Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mgallet92i/waterfall/plugin install 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/skills/mgallet92i/waterfall/wf-resume)<a href="https://agentmods.dev/skills/mgallet92i/waterfall/wf-resume"><img src="https://agentmods.dev/badge/skills/mgallet92i/waterfall/wf-resume/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/skills/mgallet92i/waterfall/wf-resume"><img src="https://agentmods.dev/badge/skills/mgallet92i/waterfall/wf-resume.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.00032 | $0.02408 |
| Opus 5 | $0.00016 | $0.01204 |
| Sonnet 5 | $0.00006 | $0.00482 |
| Haiku 4.5 | $0.00003 | $0.00241 |
Grade A, and why
wf-resume 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 10d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wf-resume — Resume an interrupted workflow
This skill is the entry point to resume a paused or interrupted waterfall need. It is invoked by the /waterfall:resume command.
Resume flow
Step 1 — Preflight (fail-fast)
bash ${CLAUDE_PLUGIN_ROOT}/scripts/wf-check-bash.sh
If not running under bash (Git Bash on Windows) → the script fails with an explicit message. STOP.
bash ${CLAUDE_PLUGIN_ROOT}/scripts/wf-check-teams.sh
If the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS flag is missing → the script fails with an explicit message. STOP.
jq verification (used by all wf scripts to parse .wf-state.json, .team-registry.json, etc.):
INSTALL_CMD=$(bash ${CLAUDE_PLUGIN_ROOT}/scripts/wf-check-jq.sh) || JQ_RC=$?
- Exit 0 → continue.
- Exit 2 →
jqmissing. If$INSTALL_CMDnon-empty,AskUserQuestion: "jq is required. Install it via${INSTALL_CMD}?" (Yes / No). On Yes:bash -c "$INSTALL_CMD"then re-run the check. On No or if command empty: display stderr and stop.
Step 1.a — Resolve WF_SID (new HO window)
Critical for statusline (INV-002): on resume, $CLAUDE_SESSION_ID is a fresh sid (new Claude Code window) that does not match the session_id stored in .wf-state.json. We must force WF_SID to the current HO sid so the --reactivate migration takes place.
export WF_SID="${CLAUDE_SESSION_ID}"
Without this, the statusline (which filters on state.session_id == $CLAUDE_SESSION_ID) will not display the resumed need.
Step 1.bis — Same-sid ambiguity detection (EX-005)
Note: when resuming in a new window,
WF_SIDis a fresh sid that won't match any state. This step is effectively a no-op on resume; it remains useful if/waterfall:resumeis invoked in the same window as a workflow that was just abandoned.
If WF_SID is set and no <name> is provided as argument:
# Count needs whose session_id == $WF_SID
matches=()
for state in C:/projets/waterfall/wf/needs/*/.wf-state.json; do
[[ -f "$state" ]] || continue
state_sid=$(jq -r '.session_id // ""' "$state" 2>/dev/null)
[[ "$state_sid" == "$WF_SID" ]] && matches+=("$(dirname "$state" | xargs basename)")
done
if [[ ${#matches[@]} -ge 2 ]]; then
# AskUserQuestion: pick among the needs (one option per need)
fi
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.
- 10d ago First seen · 182 lines · 32 tokens per session scan A 2ec9834b387b
wf-resume is a skill published in the GitHub repository mgallet92i/waterfall (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,408 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-31.
Other skills, from other repositories
start
Use this skill when the user runs /start, says "start", "enable the SDLC workflow", "I want to build", "I want to fix", "set up", "get started", or otherwise signals they want to activate or re-enable the SDLC workflow. Handles three distinct paths based on marker state — fresh install (opt-in activation), re-enable…
domain-expert
Use this skill during /plan (between scope validation and writing the plan artifact) to inject domain-specific context, gap questions, and regulatory concerns into the plan. Triggers automatically when the plan skill evaluates the task and scope.md against the domain registry in domains/index.json using semantic…
plan
Use this skill at the START of every coding task — new builds, bug fixes, and change requests. Classifies the work item, validates it against project scope, produces a high-level estimate, proposes a technology stack, and checks stack compatibility. Writes a plan artifact to .claude/sdlc/plans/ that every downstream…
configure
Use this skill when the user runs /configure, /configure --needs, or /configure --check. Also auto-invoked by env-detect.sh on fresh install (Layer 0) and by skills that find required config missing at runtime (Layer 2). Guides setup of config/tools.json and config/tools.local.json through a question bank; handles…
status
Use this skill when the user asks "where am I", "what's the current task", "what's blocking me", "show status", "what needs sign-off", or "what's next". Prints a snapshot of the active plan, gate, sign-off progress, and next action. Reads only — writes nothing.
analyze
Use this skill after Phase 1 Plan to create or intake requirements for a task. Produces requirements with stable IDs (REQ-001, REQ-002, ...), validates each requirement against the project's scope statement, and — critically — halts and asks for UX designs and brand guidelines whenever the work touches a frontend or…