Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for people running more than one agent CLI who want shared context and safer config management, instead of letting each tool drift into its own MCP and memory silo.
Who should use it
Who should skip it
Skip escoffier-labs/brigade if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
escoffier-labs/brigade is tracked by RepoRadar as a agent ops in the Coding Workflows section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, escoffier-labs/brigade is strongest on workflow potential (9.4) and open-source/build quality (8.4) and weakest on momentum (5.0) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned escoffier-labs/brigade a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Quickstart rewires local harness configs and guardrail hooks, so the first run should stay on a disposable repo or use --dry-run; The workflow assumes Brigade becomes the source of truth for shared agent wiring, so teams need to decide which existing scripts or hooks it replaces before rollout.