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/onboardgit 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.00018 | $0.01057 |
| Opus 5 | $0.00009 | $0.00528 |
| Sonnet 5 | $0.00004 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
onboard 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are onboarding brigade to an existing project. Scan the codebase and produce
.planning/ARCHITECTURE.md — a machine-readable project map that manager-agent reads
when planning sprints. This is the brownfield counterpart to /brigade:init — init sets
up roles, onboard tells brigade what already exists.
When to use
- First time setting up brigade on an existing codebase (after
/brigade:init) - After major structural changes (new services, moved directories, new tech stack)
- When
manager-agentmakes bad task decompositions because it doesn't understand the project
Step 1 — Scan project structure
Read the project root. Identify:
- Top-level layout — what lives where (
src/,apps/,packages/,server/,client/, etc.) - Package manager and monorepo tool —
package.json,pnpm-workspace.yaml,Cargo.tomlworkspace,go.work,turbo.json,nx.json - Entry points — main files, server starts, CLI entry
- Config files —
tsconfig.json,.env.example,docker-compose.yml, CI configs
Use ls, Glob, and Read on key files. Do not read every file — scan structure, read configs and entry points.
Step 2 — Identify modules and their tech stacks
For each logical module/service/package:
- Name and path
- Tech stack — language, framework, key libraries
- Role — which dev agent would own this (frontend-agent, nodejs-agent, rust-agent, golang-agent, devops-agent)
- Key files — entry point, main config, test config
Read .planning/tasks/ROLES.md if it exists — cross-reference the roles the user already picked
with what you find in the codebase.
Step 3 — Map dependencies between modules
Identify how modules talk to each other:
- Shared types/interfaces
- API boundaries (REST, gRPC, message queues)
- Shared packages in monorepo
- Database schemas shared across services
This is critical for manager-agent — it needs to know which tasks can run in parallel
(different modules) vs which have dependencies (shared interfaces).
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 · 129 lines · 18 tokens per session scan A 99a3071f6b30
onboard is a command published in the GitHub repository ushibo/brigade (1 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 1,057 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.