~ / rigs / appshapes / brigade

appshapes/brigade

Team messaging between the coding sessions of different people and machines. Claude Code, Muse Code, Codex CLI and Grok Build sessions message one another wherever they run; people without a session take part by email or Slack. One team, on

↗ GitHub ★ 6 MIT updated 2d ago project Claude CodeCodex Claude plugin
field: unknown workflow: DocsTesting & TDDDebuggingPR / code reviewCI/CD & deploy runs claude in CI
stack: GoPython
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
up to ~12.2k tokens
Claude Code loads MCP tools on demand, so the real cost is usually lower.
Heavy · median rig: 2.3k · breakdown
GUARDRAILS
1/5
No YOLO mode · details
Quality 15/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit appshapes/brigade/.claude ./rig-brigade  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit appshapes/brigade/.claude/skills/commit .claude/skills/commit
$ npx degit appshapes/brigade/.claude/skills/playwright-cli .claude/skills/playwright-cli
$ npx degit appshapes/brigade/codex/brigade/skills/email .claude/skills/email
$ npx degit appshapes/brigade/codex/brigade/skills/join .claude/skills/join
$ npx degit appshapes/brigade/codex/brigade/skills/move .claude/skills/move
$ npx degit appshapes/brigade/codex/brigade/skills/quiet .claude/skills/quiet
$ npx degit appshapes/brigade/codex/brigade/skills/sessions .claude/skills/sessions
$ npx degit appshapes/brigade/codex/brigade/skills/setup .claude/skills/setup
$ npx degit appshapes/brigade/codex/brigade/skills/slack .claude/skills/slack
$ npx degit <redacted> .claude/skills/subscribe
$ npx degit appshapes/brigade/codex/brigade/skills/team-messaging .claude/skills/team-messaging
$ npx degit appshapes/brigade/codex/brigade/skills/update .claude/skills/update
$ npx degit appshapes/brigade/codex/brigade/skills/whoami .claude/skills/whoami
$ npx degit appshapes/brigade/codex/brigade/skills/work-item-next .claude/skills/work-item-next
$ npx degit appshapes/brigade/codex/brigade/skills/work-item-start .claude/skills/work-item-start
$ npx degit appshapes/brigade/codex/brigade/skills/work-item .claude/skills/work-item
$ npx degit appshapes/brigade/codex/brigade/skills/work-items .claude/skills/work-items
$ npx degit appshapes/brigade/scripts/experiments/E0-8/plugin/skills/teammismatch .claude/skills/teammismatch
$ npx degit appshapes/brigade/scripts/experiments/E0-8/plugin/skills/teammsg .claude/skills/teammsg
$ npx degit appshapes/brigade/scripts/experiments/E0-8/plugin/skills/teamplain .claude/skills/teamplain
$ curl -fsSL --create-dirs -o .claude/agents/developer.md https://raw.githubusercontent.com/appshapes/brigade/master/.claude/agents/developer.md
$ curl -fsSL --create-dirs -o .claude/agents/documenter.md https://raw.githubusercontent.com/appshapes/brigade/master/.claude/agents/documenter.md
$ curl -fsSL --create-dirs -o .claude/agents/release-notes-email.md https://raw.githubusercontent.com/appshapes/brigade/master/.claude/agents/release-notes-email.md
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/appshapes/brigade/master/.claude/agents/reviewer.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

MCP servers (1)

serversourceest. tokens
team
env: BRIGADE_ADAPTER, BRIGADE_DATA_DIR, BRIGADE_PROFILE
local / custom 2.5k

Skills (20)

Subagents (4)

developer
model: opus
The writer/fixer role for the agentic loop — implements a labelled issue on a branch, and applies
documenter
model: opus
Keeps brigade's structural documentation — paths, make targets, versions, command names — in step
release-notes-email
model: opus
Writes and reviews the release-notes email that goes to brigade's list of recipients. Runs weekly
reviewer
model: opus
Reviews brigade pull requests against the repository's invariants and either approves or requests

Similar rigs

copied ✓