herdr-fleet SKILL.md skillB

herdr-fleet from vib-z/stampede is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add vib-z/stampede/herdr-fleet@git:20261115.b3bb0fc

Pins git:20261115.b3bb0fc in mdr.lock. Pin the fingerprint instead.

Audit grade
B, 16 of 17 checks passed
Kind
SKILL.md skill
Repository
vib-z/stampede
Path
skills/herdr-fleet/SKILL.md
Versions recorded
9
Latest version
git:20261115.b3bb0fc, committed Nov 15, 2026
First version recorded
Nov 11, 2026
Size
5,997 bytes
Repository stars
10
License
MIT

The lead's playbook for a stampede job in Herdr: plan, brief and start agents in panes or Herdr Core terminals, review on another model, merge past the owner's gates. Use when you lead a job, or a brief in Herdr asks for parallel work: every lane is a pane, never a hidden subagent.

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

# herdr-fleet

You lead one stampede job: plan it, start workers in Herdr, review their work, and bring the owner only what is theirs.
Herdr commands: `herdr --skill`. Every `stampede` command: [docs/CLI.md](../../docs/CLI.md).

## Where you are

- **Inside a Herdr pane** (`test "${HERDR_ENV:-}" = 1`): `stampede doctor`, then [tui.md](references/tui.md#look-first).
- **On Herdr Core** (`<job>/backend` is `native`): `stampede tree <job>`, then [core.md](references/core.md).
- **An external caller** (a bot, or a chat over ssh): your entry skill first (`grokbot-herdr` or `stampede`), then [tui.md](references/tui.md#from-outside-herdr).

## Size the job first: small or big

Four questions: **length** (under an hour, or hours), **agents** (one family, or a mix), **risk** (merge, push, send, spend, publish, deploy) and **durability** (must it survive a restart).

- **Small** (all four small): no stampede job. One agent with its own subagents, in a pane of its own with the `herdr-events-owner` tag, sent a [brief](references/brief.md) with `herdr-send`. Such as one bug fix.
- **Big** (any one big): a stampede job, with gates and a reopen record.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xz4tdaajkcyketat/156b47aa62ef8321cc1a4a32e38f8110fc3b269188ca24925082481b97cb9030.json

Then /plugin install herdr-fleet@markdownregistry-xz4tdaajkcyketat in Claude Code. It installs git:20261115.b3bb0fc, the one graded B here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add vib-z/stampede/herdr-fleet@sha256:156b47aa62ef8321

The line at the top of this page pins the label git:20261115.b3bb0fc, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_xz4tdaajkcyketat.svg)](https://markdownregistry.com/a/art_xz4tdaajkcyketat)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in vib-z/stampede/herdr-fleet since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of herdr-fleet from somewhere else? Ask it: where did my herdr-fleet come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 9 versions of this file, between Nov 11, 2026 and Nov 15, 2026, more than one a day. Its first recorded version is graded A and its latest B.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261115.b3bb0fc latest2026-11-15 b3bb0fc 5,997 BB view · diff
git:20261114.bd43ec82026-11-14 bd43ec8 5,991 BB view · diff
git:20261114.4758b072026-11-14 4758b07 26,939 BA view · diff
git:20261114.3f38ff42026-11-14 3f38ff4 26,894 BA view · diff
git:20261114.e2bac2a2026-11-14 e2bac2a 26,813 BA view · diff
git:20261113.29a71ad2026-11-13 29a71ad 27,344 BA view · diff
git:20261112.13c5a882026-11-12 13c5a88 27,098 BA view · diff
git:20261111.4761b072026-11-11 4761b07 26,871 BA view · diff
git:20261111.33a2d892026-11-11 33a2d89 25,445 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

B  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: No instruction to read or print local credentials (matched: read, copy or print credentials or `.env)
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (5997 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 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

GitHub

vib-z/stampede · 10 stars · license MIT · pushed 2026-11-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_xz4tdaajkcyketat
GET https://markdownregistry.com/api/v1/resolve?ref=vib-z/stampede/herdr-fleet
GET https://markdownregistry.com/api/v1/blob/156b47aa62ef8321cc1a4a32e38f8110fc3b269188ca24925082481b97cb9030

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 vib-z/stampede

AGENTS.md AGENTS.md file
vib-z/stampede · AGENTS.md
git:20261115.fed9af0 · audit A · 10 stars
CLAUDE.md CLAUDE.md file
vib-z/stampede · CLAUDE.md
git:20261114.e2bac2a · audit A · 10 stars
stampede SKILL.md skill
vib-z/stampede · SKILL.md · One ask starts a Herdr job run by a lead agent that opens panes only when it's worth it. Use when asked to use…
git:20261114.901a40d · audit A · 10 stars
grokbot-herdr SKILL.md skill
vib-z/stampede · skills/grokbot-herdr/SKILL.md · FIRST skill to read whenever a Grok Bot, or any bot outside Herdr, needs Herdr on the owner's machine: connect over…
git:20261114.901a40d · audit A · 10 stars
share-plan SKILL.md skill
vib-z/stampede · skills/share-plan/SKILL.md · Use only when the owner explicitly asks to see or approve the plan before work starts ("share the plan first", "show me…
git:20261114.cc812ad · audit A · 10 stars
stampede SKILL.md skill
vib-z/stampede · skills/stampede/SKILL.md · The front door for stampede, from any project chat (Claude desktop, a terminal or a Herdr pane). Use when the owner…
git:20261115.b3bb0fc · audit A · 10 stars

Every file in vib-z/stampede

Browse by kind, by grade B, or by owner.