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/initgit 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.00024 | $0.03047 |
| Opus 5 | $0.00012 | $0.01523 |
| Sonnet 5 | $0.00005 | $0.00609 |
| Haiku 4.5 | $0.00002 | $0.00305 |
Grade A, and why
init 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 yesterday.
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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are bootstrapping the brigade plugin for the user's current project. This is the
single entry point for setup: role selection, stack configuration, rule activation, and
sprint-workflow scaffolding.
Step 1 — List what is available
Run these first. Do not hardcode any names — always read from disk:
ls ~/.claude/plugins/brigade/agents/— every agent file is one available role.ls ~/.claude/plugins/brigade/presets/— stack presets.ls ~/.claude/plugins/brigade/rules/— individual rule files.
For each agent, read the name and description fields from its frontmatter. For each
preset, read the first heading and the short description block.
Step 2 — Ask which roles this project needs
Show a numbered checklist grouped logically. Example:
Which roles does this project need? (pick one or many, e.g. "1,3,5")
Development
1. frontend — React/Vue/Svelte, app logic, routing, state
2. designer — UI/UX, design systems, visual direction, styled components
3. nodejs — Node.js services, APIs, integrations
4. golang — Go services, CLI, microservices
5. devops — infra, CI/CD, k8s, cloud
0. skip — exit without changes
review-agentis always auto-included when any dev role is picked. Do not show it in the list.manager-agentis always included — it is the orchestrator. Do not show it in the list.- Specialist reviewers (
silent-failure-reviewer,test-coverage-reviewer,type-reviewer) and Bug Council agents are spawned conditionally by/brigade:runand/brigade:bug-council. Do not show them in the list.
Wait for the user's selection. Do not proceed until they reply.
Step 3 — Configure each picked role
For each selected role, check whether any preset or rule file applies to it. Today:
| Role | Ask about | Options |
|---|---|---|
| frontend | Which React flavour? | react-mobx-strict, react-basic, or no rules |
| nodejs | Which backend framework? | nodejs-fastify, nodejs-express, nodejs-nestjs, or no rules |
| designer, golang, devops | no presets yet | skip |
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.
- yesterday First seen · 267 lines · 24 tokens per session scan A 9d69919eeba1
init is a command published in the GitHub repository ushibo/brigade (1 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 3,047 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
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
create
Scaffold a new plugin with directory structure, manifests, and marketplace registration.
compose-stack
Compose a sequenced Intelligence Stack Plan for a sovereign person. Analyzes their Genius Profile + Freedom Path + stated priorities + life stage, then sequences which of the 9 layers activate first, second, third. Produces a 90-day sprint plan for building their full intelligence stack. For humans with Genius Profile…
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Auto-creates PR unless --no-pr flag is passed.
develop
Implement skill development issues with TDD-governed workflow.
dev-task
Create an agent team to develop: Developer teammate + Code-tester teammate + QA-tester teammate + Reviewer teammate + Researcher subagent → implements .dev/cdt/plans/plan-$TIMESTAMP.md in waves.