setup SKILL.md skillB
setup from appshapes/brigade is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add appshapes/brigade/setup@git:20261017.a9fa483Pins git:20261017.a9fa483 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- appshapes/brigade
- Path
plugin/skills/setup/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261017.a9fa483, committed Oct 17, 2026
- First version recorded
- Sep 8, 2026
- Size
- 11,330 bytes
- Repository stars
- 4
- License
- MIT
How a HUMAN creates or joins a Brigade team — `team create` with the `!` prefix inside a session or from a terminal, `/brigade:join <path>` to join — and how to leave and uninstall: the Supabase project prerequisites, `team create` (which writes the project's committed `.brigade.json`), the one-line `/brigade:join <path>`, and the removal order. Use when someone asks how to set Brigade up, join a team, add a teammate, leave, or remove the plugin. It never asks anyone to paste a join secret…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Setting Brigade up
A Brigade team belongs to a **project**: a committed file, `.brigade.json`, at the repository's top level names the
team every session in that checkout talks to. It carries only public values, so it is safe in version control; the
join secret is never in it. The administrator writes the file once; each member runs one command in their checkout.
The file may carry optional members the project commits by hand: `sync` (folders to keep in step), `gateway` (how
people without a session reach the team) and `polling` (how often sessions check in with the backend, to stay
inside a plan's request budget, and how long a session the VS Code extension started may stay idle before it
closes itself). `docs/team-admin/configure/team-file.md` in the Brigade repository describes each.
Every command below is the **person's** to run. Inside a Claude Code session the `!` prefix runs it on the Bash
tool's PATH, where `brigade` already is, and its output lands in the conversation — never a secret. In a terminal
the same command runs through the binary at `${CLAUDE_PLUGIN_ROOT}/bin/brigade`; a symlink such as
…Read the whole file at its exact version.
How to install
mdr add appshapes/brigade/setup@sha256:d4e5f5d7ba9e072fThe line at the top of this page pins the label git:20261017.a9fa483, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_chqsn3ldoxb65bd5)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Sep 8, 2026 and Oct 17, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.a9fa483 latest | 2026-10-17 | a9fa483 | 11,330 B | B | view · diff |
| git:20261007.38570ed | 2026-10-07 | 38570ed | 11,216 B | B | view · diff |
| git:20261006.71a5a40 | 2026-10-06 | 71a5a40 | 9,946 B | B | view · diff |
| git:20261006.74e6804 | 2026-10-06 | 74e6804 | 9,854 B | B | view · diff |
| git:20261006.3838da0 | 2026-10-06 | 3838da0 | 9,553 B | B | view · diff |
| git:20260917.e00c116 | 2026-09-17 | e00c116 | 9,234 B | B | view · diff |
| git:20260913.6f16342 | 2026-09-13 | 6f16342 | 7,905 B | B | view · diff |
| git:20260908.63318f8 | 2026-09-08 | 63318f8 | 7,787 B | B | view · diff |
| git:20260908.4bac16d | 2026-09-08 | 4bac16d | 7,756 B | B | view · diff |
| git:20260908.7fc45be | 2026-09-08 | 7fc45be | 7,642 B | B | view |
Audit of the latest version
- fail: No recursive delete of root, home or parent (matched: rm -rf ~/)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11330 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
appshapes/brigade · 4 stars · license MIT · pushed 2026-10-19 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_chqsn3ldoxb65bd5 GET https://markdownregistry.com/api/v1/resolve?ref=appshapes/brigade/setup GET https://markdownregistry.com/api/v1/blob/d4e5f5d7ba9e072fccbbf5c876b0f2edd18cd4de038ac86f1b9262f5e0f4b6ea
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from appshapes/brigade
Every file in appshapes/brigade