verify-brigade SKILL.md skillA
verify-brigade from escoffier-labs/brigade is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add escoffier-labs/brigade/verify-brigade@git:20261017.4984b1cPins git:20261017.4984b1c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- escoffier-labs/brigade
- Path
registry/skills/verify-brigade/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.4984b1c, committed Oct 17, 2026
- First version recorded
- Sep 1, 2026
- Size
- 16,222 bytes
- Repository stars
- 78
- License
- MIT
Prove a Brigade change works by driving the real `brigade` CLI against a throwaway temp target, then capture receipts as evidence. Use when you changed anything under src/brigade/ and need proof beyond pytest - init/doctor wiring, work-verify receipts, Grok Bot connector packs, feed manifests, handoff lint. Also use before claiming a CLI behavior in a PR body, handoff, or job report.
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
# Verify Brigade This skill verifies the `brigade` CLI against a temp target. The optional Center dashboard is a separate surface. Run the CLI and read what it wrote. This skill drives it through one helper, `control-brigade.py`, so a proof is a rerunnable command instead of a story. Every drive happens in a temp target this skill creates. The helper enforces that: `--target` is accepted only when it resolves *under* `<state-root>/targets`, so the operator home, the Brigade checkout, and every other path are refused before a command runs. The state root gets the same treatment whether it comes from `--root` or from the default - resolved, refused if it resolves to or contains the home directory or the checkout, and refused if it is a symlink at the root or at `targets/`/`captures/`, so a link planted in a world-writable temp dir cannot redirect a drive. `cleanup` removes only paths `new-target` recorded. `AGENTS.md` forbids driving the real workspace anyway; here it is not reachable. What that paragraph does *not* claim: - A path under the temp base is allowed even when `$TMPDIR` sits inside the home directory. That is the only carve-out, and it is exactly that narrow: …
Read the whole file at its exact version.
How to install
mdr add escoffier-labs/brigade/verify-brigade@sha256:c4223de592388cafThe line at the top of this page pins the label git:20261017.4984b1c, 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_gfmk5wmxorlih4so)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 1, 2026 and Oct 17, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.4984b1c latest | 2026-10-17 | 4984b1c | 16,222 B | A | view · diff |
| git:20260902.faddc7c | 2026-09-02 | faddc7c | 16,256 B | A | view · diff |
| git:20260902.644cb4c | 2026-09-02 | 644cb4c | 11,108 B | A | view · diff |
| git:20260901.da171ee | 2026-09-01 | da171ee | 10,840 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 (16222 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
escoffier-labs/brigade · 78 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gfmk5wmxorlih4so GET https://markdownregistry.com/api/v1/resolve?ref=escoffier-labs/brigade/verify-brigade GET https://markdownregistry.com/api/v1/blob/c4223de592388caf0d15982a2174d3f829007ca6fe4fe124a9953299e886880e
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.