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 skills add escoffier-labs/brigade --skill forward-plangit clone --depth 1 https://github.com/escoffier-labs/brigadeWrote 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/escoffier-labs/brigade/forward-plan)<a href="https://agentmods.dev/skills/escoffier-labs/brigade/forward-plan"><img src="https://agentmods.dev/badge/skills/escoffier-labs/brigade/forward-plan/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/escoffier-labs/brigade/forward-plan"><img src="https://agentmods.dev/badge/skills/escoffier-labs/brigade/forward-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 195 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00073 | $0.02403 |
| Opus 5.5 | $0.00029 | $0.00961 |
| Sonnet 5.5 | $0.00015 | $0.00481 |
| Haiku 4.5 | $0.00007 | $0.00240 |
Grade A, and why
forward-plan 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 1mo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
forward-plan
Turn the native ready set, outcome ranking, and the repo ROADMAP into one dependency-filed plan artifact. Brigade stays invoke-only. This skill is the allowlist-bound agent recipe. It is a registry skill, never a CLI subcommand - the planning sequence stays inspectable.
When this applies
- You need a forward plan that joins what is ready now with roadmap direction.
- An operator schedules a headless harness against this skill for planning.
- The workspace has (or can create)
.brigade/work/and may or may not have GraphTrail installed.
Allowlist
Work only through this allowlist:
brigade work ready --json(add--explainwhen blocked items matter)brigade outcome rank --json(optional--by-capability/--recency)- Read of repo-root
ROADMAP.mdunder the parse contract below brigade code …for GraphTrail footprint / impact / doctor checksbrigade work task edge …/brigade work task add --graph …only after an operator confirms derived edges (never auto-apply. See Safety gates)brigade work plansto list existing plan artifacts- Write only under
.brigade/work/plans/(the plan JSON + plan.md pair) - Read/Grep of on-disk task ledgers, existing plans, and code paths named by GraphTrail output
Bash is scoped to those brigade … commands only. Do not expand into arbitrary
shell, remote APIs, or writes outside .brigade/work/plans/. Stay inside the
target workspace. Do not follow .. or symlinks out of it.
Safety gates
Plan draft is not graph-ingest input. A forward-plan draft under
.brigade/work/plans/ (the .json / .plan.md pair) is not valid input
to brigade work task add --graph. That command expects a graph-ingest file
shaped for task creation with edges. Feeding it a plan draft can create task
nodes while applying zero proposed edges from proposed_edges.
Confirmation is procedural, not enforced by the allowlist. Derived-edge
confirmation is an operator-in-the-loop gate. The broad
Bash(brigade work task:*) allowed-tool pattern does not enforce it, so this
recipe must not run any mutating brigade work task … or
brigade work task edge … command before the operator gives explicit
confirmation.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 198 lines · 73 tokens per session scan A 2f298c45bfd1
forward-plan is a skill published in the GitHub repository escoffier-labs/brigade (81 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 2,403 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
capture-task
Capture a new task — create a draft or pending Task record from a rough idea or detailed spec. Use when asked to "add a task", "log a bug", "create a task", or "add to backlog".
refine-backlog
Refine the backlog — screen drafts, remove duplicates, fill in missing details, classify, link, and move to pending.
implement-task
Pick up and work on a binder Task — investigate bugs, discuss open questions, design solutions, write tests, or implement code. Use when asked to "work on", "pick up", "implement", or "fix" a task.
execplan-run
Execute and CLOSE an ExecPlan end-to-end in CueCrux — the execution half that execplan-synthesize/appraise/research (authoring half) hand off to. Runs the milestone loop: claim from the ranked board, announce focus for collision detection, worktree, implement, gate fact, PR, shepherd checks, merge, next milestone…
bo-process-optimization
A method for examining a business workflow to find waiting, rework, handoff waste, and other delays, then proposing improvements and ways to measure them. It separates observed facts from possible explanations and suggestions.
bo-risk-assessment
A method for assessing operational risks in a process, project, or supplier arrangement using observed facts, possible consequences, and practical response suggestions. It keeps the likelihood of a consequence conditional unless the evidence supports more.