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/ushibo/brigade/resumegit clone --depth 1 https://github.com/ushibo/brigadeWhat 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.00023 | $0.01469 |
| Opus 5 | $0.00012 | $0.00734 |
| Sonnet 5 | $0.00005 | $0.00294 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
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 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are resuming a sprint that was interrupted. Auto-detect the state and continue from the right place. This command covers three scenarios:
- Interrupted run —
/brigade:runwas stopped mid-wave (session crashed, user pressed ctrl+c, or workers hung). Pick up where it stopped. - Manual merge recovery — a wave halted on review findings, user fixed them manually, now wants to merge outstanding branches and continue.
- Forgotten state — user came back after days/weeks and doesn't remember what's done.
Do not delegate orchestration to manager-agent — subagents can't spawn further subagents. This command runs at the top level.
Preflight
- Verify
.planning/tasks/ROLES.mdexists. If missing, stop and tell the user to run/brigade:init. - Verify the working tree is clean (
git status). If dirty, ask the user to commit or stash and stop. - Confirm you are on
mainormaster. If not, ask the user to check out the base branch and stop.
Step 1 — Detect current state
Read these inputs, in order:
- Current sprint: list
.planning/tasks/sprint-*/, pick highest-numbered. Read_README.md. - Task statuses: scan every
S{N}.{M}-*.mdspec file forstatus:field. Count done / in-progress / todo / blocked. - Git branches:
git branch --list 'feat/*' --no-merged main. These are outstanding branches that never got merged. - Commits on main not yet recorded:
git log --oneline main ^{base}filtered byfeat: s{N}.{M}patterns. Find tasks whose commits are already on main but whose spec still saysstatus: todo. - Review reports:
ls .planning/tasks/sprint-{N}/reviews/— which waves have review reports, what were the verdicts.
Step 2 — Classify the situation
Based on inputs, pick ONE of these scenarios and proceed accordingly.
Scenario A: Status drift only
Some tasks have commits on main (feat: s{N}.{M} in log) but their spec still says status: todo.
Action:
- For each drifted task, update its spec frontmatter →
status: done. - Mark completed in sprint
_README.md. - Commit:
chore: sync sprint statuses. - Re-run state detection. May unlock Scenario B/C/D.
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 · 127 lines · 23 tokens per session scan A 55d914a96b42
resume is a command published in the GitHub repository ushibo/brigade (1 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,469 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-08-31.
Other commands, from other repositories
hire-assess-fit
Run a culture-add fit assessment for a candidate (NOT culture-fit). Names what the team currently lacks, names what this candidate adds, runs gap-bridge analysis. Refuses generic "great culture fit" framing — culture-fit reproduces, culture-add expands. Used as a SUPPLEMENT to the structured rubric, never as a…
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
earnings-week
Upcoming earnings + dividend events for portfolio holdings over next N weeks (default 2). Surfaces event clusters (multiple positions on same day = concentrated event risk), consensus estimates, key questions to watch. Run before FOMC/earnings-heavy weeks.
eval
View agent evaluations and detect regressions.
auto
AI auto strategy executor. Analyzes task and automatically selects and executes the best strategy: direct execution, hybrid-auto PRD generation, hybrid-worktree isolated development, or mega-plan multi-feature orchestration.