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.
npx skills add owainlewis/agent-skills --skill herdr-issue-coordinatorgit clone --depth 1 https://github.com/owainlewis/agent-skillsWrote 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.
[](https://agentmods.dev/skills/owainlewis/agent-skills/herdr-issue-coordinator)<a href="https://agentmods.dev/skills/owainlewis/agent-skills/herdr-issue-coordinator"><img src="https://agentmods.dev/badge/skills/owainlewis/agent-skills/herdr-issue-coordinator/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.
<a href="https://agentmods.dev/skills/owainlewis/agent-skills/herdr-issue-coordinator"><img src="https://agentmods.dev/badge/skills/owainlewis/agent-skills/herdr-issue-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00068 | $0.03109 |
| Opus 5 | $0.00034 | $0.01554 |
| Sonnet 5 | $0.00014 | $0.00622 |
| Haiku 4.5 | $0.00007 | $0.00311 |
Grade A, and why
herdr-issue-coordinator 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Herdr issue coordination
Use this session as the coordinator. Give each dispatched GitHub issue its own git worktree, branch, Herdr tab, and Claude Code session. Sequence the work. Keep implementation context in workers and all durable state in GitHub.
This skill is experimental. It depends on the herdr CLI and its API changes
between versions. Verify the commands below against the installed binary before
relying on them.
Explicitly naming /herdr-issue-coordinator, or explicitly telling the
coordinator that agents may merge, authorizes in-scope workers to merge their
own pull requests after every merge gate below passes. An implicit skill match
does not grant merge authority: run in no-merge mode unless the user's words
grant it. Neither mode authorizes deployment, release publication, destructive
operations, branch-protection bypasses, or changes outside the supplied batch.
Preconditions
Stop if any of these fail. Do not substitute hidden subagents for workers.
test "${HERDR_ENV:-}" = 1. You must be running inside a Herdr pane.herdr --versionreports 0.8.0 or later. Earlier versions have noagent promptand noagent start --pane, and this skill will not work.herdr agentlistsprompt, andagent startaccepts--kindand--pane. The binary is the authority, not this document.- The working directory is a git repository with a GitHub remote and
ghauthenticated. - Read the repository instructions, parent issue, sub-issues, declared dependencies, project board, issue state, and linked open or merged pull requests. A merged pull request is only evidence of completion when it closes or explicitly references the issue and its final change and proof satisfy the issue scope. Reconcile that state instead of dispatching again.
- Make every issue a complete task before dispatch. If a missing product or technical decision could change behavior, data, security, compatibility, operations, cost, or proof, mark that issue as needing human input.
- Build a dependency graph. Stop for human correction on a dependency cycle.
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.
- 10d ago First seen · 285 lines · 68 tokens per session scan A 5153e8b91d12
herdr-issue-coordinator is a skill published in the GitHub repository owainlewis/agent-skills (44 stars, last pushed 19d ago), licensed MIT. It adds 68 tokens to every session and 3,109 once invoked, about $0.0003 per session on Opus 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-08-30.
Other skills, from other repositories
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.