sessions SKILL.md skillA
sessions 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/sessions@git:20260927.8404371Pins git:20260927.8404371 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- appshapes/brigade
- Path
plugin/skills/sessions/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260927.8404371, committed Sep 27, 2026
- First version recorded
- Sep 13, 2026
- Size
- 2,797 bytes
- Repository stars
- 4
- License
- MIT
Show the team's sessions: `/brigade:sessions` runs `brigade sessions` and prints its output unchanged. `/brigade:sessions --all` includes the offline ones, `/brigade:sessions --here` shows only this repository's, and `/brigade:sessions --member <who>` only one member's. Use it whenever the roster is being SHOWN to the user, so they see what the command printed rather than a retelling of it; reading the roster to address a message is `brigade:team-messaging`.
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
# Show the team's sessions `$ARGUMENTS` is what came after the command name: typed by the user through `/brigade:sessions`, or passed by you when you loaded this skill to show the roster — a flag only when the user asked for what it does, otherwise nothing. Either way the steps below are the whole of it. 1. Build the command from `$ARGUMENTS`, ignoring surrounding whitespace. These are the only forms: | `$ARGUMENTS` | Run exactly | | --- | --- | | empty | `brigade sessions` | | `--all` | `brigade sessions --all` | | `--here` | `brigade sessions --here` | | `--member <who>` | `brigade sessions --member '<who>'` | `--all`, `--here` and `--member <who>` may be combined, in any order, each at most once: `brigade sessions --all --here --member '<who>'`. `<who>` is a member's label as the `MEMBER` column shows it, or the first 8 or more characters of their principal reference, or a bracketed `MEMBER` cell such as `[9f3c1a20]`. Put it in single quotes, as one argument. If it holds a single quote, a backslash or a line break, say that this skill cannot pass it, and stop. …
Read the whole file at its exact version.
How to install
mdr add appshapes/brigade/sessions@sha256:901662ca07232be6The line at the top of this page pins the label git:20260927.8404371, 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_dxhxfmlytddr4tg3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 13, 2026 and Sep 27, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.8404371 latest | 2026-09-27 | 8404371 | 2,797 B | A | view · diff |
| git:20260927.cd6684c | 2026-09-27 | cd6684c | 1,954 B | A | view · diff |
| git:20260920.4048018 | 2026-09-20 | 4048018 | 1,976 B | A | view · diff |
| git:20260920.eee93c6 | 2026-09-20 | eee93c6 | 1,893 B | A | view · diff |
| git:20260913.2731453 | 2026-09-13 | 2731453 | 1,614 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 (2797 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_dxhxfmlytddr4tg3 GET https://markdownregistry.com/api/v1/resolve?ref=appshapes/brigade/sessions GET https://markdownregistry.com/api/v1/blob/901662ca07232be68db6e1115c42d7336cd1228de0c9d14eb478f4453401f9d2
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