herdr-agents

herdr-agents is a skill for Claude Code, Codex from skrrt-sh/skills. It costs 116 tokens per session (1,311 once invoked), scanned A, original, MIT.

A workflow for running coding subagents in Herdr, with one named agent and Git worktree per task. A worktree is a separate checkout of the repository, so agents can work in parallel without sharing the same files.

In plain words
What is it for?
Use it inside Herdr to dispatch scoped tasks, exchange status mail with child agents, integrate their changes, and clean up their worktrees.
Why use it?
It separates parallel changes and provides messages about child-agent completion, blocking, or exit. It also removes the temporary worktrees after integration.

Skill for Claude CodeCodex

Written for Claude Code and Codex: ${CLAUDE_SKILL_DIR} variable, but also agents/openai.yaml present. Also seen: mentions subagents.

Part of the dev plugin — 7 skills shipped together

Good fit Use it inside Herdr to dispatch scoped tasks, exchange status mail with child agents, integrate their changes, and clean up their worktrees.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/skrrt-sh/skills/herdr-agents
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add skrrt-sh/skills --skill herdr-agents
Clone the repo
git clone --depth 1 https://github.com/skrrt-sh/skills

Made for: Claude Code, Codex.

Or install dev, the plugin that ships this one along with the rest of its 7 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for herdr-agents

README.md
[![agentmods](https://agentmods.dev/badge/skills/skrrt-sh/skills/herdr-agents/github.svg)](https://agentmods.dev/skills/skrrt-sh/skills/herdr-agents)
Your own site
<a href="https://agentmods.dev/skills/skrrt-sh/skills/herdr-agents"><img src="https://agentmods.dev/badge/skills/skrrt-sh/skills/herdr-agents/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for herdr-agents

Your own site · 80×15
<a href="https://agentmods.dev/skills/skrrt-sh/skills/herdr-agents"><img src="https://agentmods.dev/badge/skills/skrrt-sh/skills/herdr-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,311 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00116 $0.01311
Opus 5.5 $0.00046 $0.00524
Sonnet 5.5 $0.00023 $0.00262
Haiku 4.5 $0.00012 $0.00131

Measured 3d ago against content hash dfae6015b8ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

herdr-agents scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/dev/herdr-agents/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Herdr Agents

The subagents skill decides the scopes. This skill runs each scope in its own checkout.

Guard: test "${HERDR_ENV:-}" = 1. If it fails, say so and dispatch with the Agent tool. Read-only Explore work always uses the Agent tool.

Mail

The bundled herdr-mail plugin holds mail until the recipient is idle. Its hooks mail each child's done, blocked, and exited states to the parent. Check it once per run:

mail="${CLAUDE_SKILL_DIR}/assets/herdr-mail/bin/herdr-mail"
herdr plugin list --json | jq -e --arg r "${CLAUDE_SKILL_DIR}/assets/herdr-mail" \
  '.result.plugins[] | select(.plugin_id == "skrrt.herdr-mail" and .plugin_root == $r)'

No match: ask the user, then run herdr plugin link "${CLAUDE_SKILL_DIR}/assets/herdr-mail". It runs in every Herdr session. Suggest allowing Bash(<$mail path>:*), or each child stops on a permission prompt at its first send.

Dispatch

Once per run, confirm herdr worktree create, herdr agent start, and $mail are allowed. If not, ask the user once for the rules, not per agent.

Once per stage, snapshot the base: base=$(git stash create), or HEAD on a clean tree. It captures the integrated earlier stages without committing or signing.

Per scope. Name the agent after the scope, matching [a-z][a-z0-9_-]{0,31}. Read every ID from JSON.

ws=$(herdr worktree create --cwd "$PWD" --branch "scope/$name" --base "${base:-HEAD}" --label "$name" --no-focus)
pane=$(jq -r .result.root_pane.pane_id <<<"$ws")    # also keep .result.workspace.workspace_id
herdr agent start "$name" --kind claude --pane "$pane" -- --model opus
"$mail" watch "$name"
herdr agent prompt "$name" "$(cat <<'EOF'
<brief, ending with the protocol below>
EOF
)" --wait --until working --timeout 30000
  • --until working confirms delivery and returns. Start the whole stage before waiting on any agent.
  • Use another kind, model, or permission mode only when the user names one.
  • Install dependencies in the checkout before prompting. Get its path from herdr worktree list --cwd "$PWD". Never copy .env files into it.
  • Never seed a checkout with a patch or share one checkout between agents.
  • New work gets a new agent and worktree. Never re-brief a finished agent.

Read the full file on GitHub · 100 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 100 lines · 116 tokens per session scan A dfae6015b8ee

Subscribe to this mod's changes

herdr-agents is a skill published in the GitHub repository skrrt-sh/skills (2 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 1,311 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-22.

Related

Other skills, from other repositories

commit-push-pr

Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.

sneg55/agent-starter · 28 tokens

commit

Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.

sneg55/agent-starter · 35 tokens

fix-github-issue

Turn one known GitHub issue into a merged pull request, headless: a worker in its own git worktree, a draft pull request carrying its proof, an isolated second-engine reviewer, and a serial pull master that checks import-closure staleness against the base before it merges. Use when the task is "fix issue N…

simiancraft/simiancraft-skills · 161 tokens

changelog-assembly

This skill should be used when the user mentions "changelog", "release notes", "keep a changelog", "conventional commits", "commit message", "what changed", or "release summary". Provides a standardized methodology to turn raw, possibly non-conventional git history into human-readable changelogs and release notes.

sigistry/marketplace · 70 tokens

git-for-research-code

When the user wants to version-control optimization research code - small commits per experiment change, tags for paper result snapshots, .gitignore for solver logs, linking result tables to commit hashes, and branch strategy for risky refactors. Also use when the user mentions "git workflow," "version control…

hajibabaie/combinatorial-optimization-skills · 117 tokens

avi-pr-flow

Automate PR workflow with commit, push, create PR, and review cycle.

avi1234/claude-team-plugins · 15 tokens