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:20261017.060f486Pins git:20261017.060f486 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- appshapes/brigade
- Path
codex/brigade/skills/team-messaging/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261017.060f486, committed Oct 17, 2026
- First version recorded
- Oct 17, 2026
- Size
- 23,592 bytes
- Repository stars
- 4
- License
- MIT
Message the coding sessions of OTHER PEOPLE on your Brigade team (cross-user, cross-machine; Codex CLI, Claude Code and Muse Code sessions alike) with the `brigade` CLI, reach people on email or Slack through the team's gateways (a body whose first line is `to: <address>`, `to: @name` or `to: #channel`), and handle incoming <brigade-message> frames. Use when asked to tell, ask, notify or hand off to a teammate's session, to email or Slack a person or a channel, when asked who is on the team…
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 coding sessions — Codex CLI, Claude Code and Muse Code — that belong to **different people and machines** in one team. It is not `codex queue`, which reaches only Codex threads of your own account on this machine. This is a Codex CLI session: `brigade` is the bootstrap the session-start line named (the plugin's `bin/brigade`; the bare word works when it is on your PATH); run it through your shell tool, **one `brigade` command per call**. **Team messages reach this session as turns of their own**: Brigade's watcher queues each one into this session from outside, so it appears as a `<brigade-message …>` frame that your user did not type, and is handled as the Receiving section says. There is nothing to arm and nothing to poll; a resumed session (`codex resume`) registers again at its first prompt. | Need | Use | | --- | --- | | Your own Codex threads on this machine | `codex queue` | | A teammate's session (another person, any machine, any harness) | `brigade sessions`, `brigade send` | ## Quick start ```bash # who is on the team right now; the SESSION column is the address brigade sessions …
Read the whole file at its exact version.
How to install
mdr add appshapes/brigade/team-messaging@sha256:e3f6156f9b60c824The line at the top of this page pins the label git:20261017.060f486, 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_kamikfnig3z2eszy)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 17, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.060f486 latest | 2026-10-17 | 060f486 | 23,592 B | A | view · diff |
| git:20261017.de13cc7 | 2026-10-17 | de13cc7 | 23,512 B | A | view |
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 (23592 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_kamikfnig3z2eszy GET https://markdownregistry.com/api/v1/resolve?ref=appshapes/brigade/team-messaging GET https://markdownregistry.com/api/v1/blob/e3f6156f9b60c82412c8c6fe7373f34d41a0013988a4d71af6b07507264668f9
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