Brigade is an ecosystem for running crews of AI agents as a personal intelligence system, with local handling of credentials and support for exposing agent crews to the internet for testing. It is for people who want to organize and operate multiple AI agents using their own API keys or existing Claude, ChatGPT, Copilot, Claude Code, or Codex access. The catalogue skills provide workflows for using Brigade and its agent ecosystem.
Borrowing it
Nothing to install: this file belongs to spinabot/brigade. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/spinabot/brigade/main/AGENTS.mdgit clone --depth 1 https://github.com/spinabot/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/instructions/spinabot/brigade/agents-md)<a href="https://agentmods.dev/instructions/spinabot/brigade/agents-md"><img src="https://agentmods.dev/badge/instructions/spinabot/brigade/agents-md/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/instructions/spinabot/brigade/agents-md"><img src="https://agentmods.dev/badge/instructions/spinabot/brigade/agents-md.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.03380 | $0.03380 |
| Opus 5.5 | $0.01352 | $0.01352 |
| Sonnet 5.5 | $0.00676 | $0.00676 |
| Haiku 4.5 | $0.00338 | $0.00338 |
Grade A, and why
brigade AGENTS.md 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 2mo 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Working in the Brigade codebase
This guide is for humans and AI coding agents contributing to Brigade. It covers the layout, the commands, the conventions you must follow, and the recipes for common changes. Read it before you touch the tree.
For user-facing docs see README.md. For the release flow see docs/RELEASING.md.
What Brigade is
A single-operator, multi-agent AI-crew runtime written in TypeScript. It runs as a
headless WebSocket gateway (the state-holding daemon) with thin clients (a chat
TUI, connect, channel adapters). It is built on the pi SDK
(@earendil-works/pi-agent-core + @earendil-works/pi-ai +
@earendil-works/pi-coding-agent + @earendil-works/pi-tui, pinned exact at
0.79.9) and adds product layers on top: memory, skills, sub-agents, tools, an org
hierarchy, channels, cron, an extension SDK, and a dual-mode storage layer.
- Stack: TypeScript (strict), ESM, Node ≥ 22.12, npm (never pnpm).
- Build:
tsc→dist/. No bundler. - Tests: Node's built-in
node:test, run viatsx. - State: everything under
~/.brigade/(override:BRIGADE_STATE_DIR).
Naming & brand conventions (MUST follow)
- The product is Brigade. In code, comments, copy, CLI help, error messages,
env vars, daemon labels, and docs, refer to the agent SDK only as
pi/@earendil-works/pi-coding-agent. Do not name other third-party AI agent projects. - Never commit secrets, real personal data (names, phone numbers, emails), or
local absolute paths. Use placeholders (
+1 555 010 0001,/path/to/project). - The mascot is 🦁 the Pride. No other animal/symbol.
templates/workspace/holds default persona files and is off-limits: behavioural fixes go in code, never in template content.- No
Co-Authored-Bytrailers on commits.
Daemon labels (don't rename): macOS launchd com.brigade.gateway, Linux systemd
brigade-gateway, Windows Task Scheduler BrigadeGateway.
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.
- 2mo ago First seen · 263 lines · 3,380 tokens per session scan A d30fe42714da
brigade AGENTS.md is an instructions file published in the GitHub repository spinabot/brigade (11,365 stars, last pushed 6d ago), licensed MIT. It adds 3,380 tokens to every session, about $0.0135 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.