team-messaging SKILL.md skillA
team-messaging 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/team-messaging@git:20260830.66174aaPins git:20260830.66174aa in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- appshapes/brigade
- Path
docs/research/plugin-bootstrap-cli.files/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260830.66174aa, committed Aug 30, 2026
- Size
- 5,117 bytes
- Repository stars
- 4
- License
- MIT
Message the Claude Code sessions of OTHER PEOPLE on your Brigade team (cross-user, cross-machine) with the `brigade` CLI, and handle incoming <brigade-message> frames. Use when asked to tell, ask, notify or hand off to a teammate's session, when asked who is on the team, or whenever a <brigade-message> frame arrives.
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
# Brigade team messaging with the `brigade` CLI Brigade connects Claude Code sessions that belong to **different people and machines** in one team. It is not the built-in `ListAgents` / `SendMessage`, which reach only your own sessions. `brigade` is on PATH while the plugin is enabled; run it through the Bash tool. | Need | Use | | --- | --- | | Your own sessions (this machine, Remote Control, cloud) | built-in `ListAgents`, `SendMessage` | | A teammate's session (another person, any machine) | `brigade sessions`, `brigade send` | ## Quick start ```bash # who is on the team right now (session_id is the address; names can collide) brigade sessions # send a message; the body always travels on stdin, never on the command line brigade send <session_id> --summary "Migration landed" <<'EOF' The tenant_id migration is merged on master. Nothing to do on your side. EOF ``` ## Commands ```bash brigade sessions # teammates' sessions: session_id, name, human label, state, inbound policy brigade sessions --all # include offline sessions brigade whoami # this session's Brigade session_id, name and team …
Read the whole file at its exact version.
How to install
mdr add appshapes/brigade/team-messaging@sha256:34c1b08120790c1fThe line at the top of this page pins the label git:20260830.66174aa, 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_4rk6jykih6hdr4gc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 30, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5117 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 recursive delete of root, home or parent
- 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
Source
appshapes/brigade · 4 stars · license MIT · pushed 2026-10-19 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_4rk6jykih6hdr4gc GET https://markdownregistry.com/api/v1/resolve?ref=appshapes/brigade/team-messaging GET https://markdownregistry.com/api/v1/blob/34c1b08120790c1fb2c5dcffc506cc167e824d9fb94b40f3c2f580a8d65a2c8d
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