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 transparent-pegasus/herdrpowers --skill orchestrationgit clone --depth 1 https://github.com/transparent-pegasus/herdrpowersWrote 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/transparent-pegasus/herdrpowers/orchestration)<a href="https://agentmods.dev/skills/transparent-pegasus/herdrpowers/orchestration"><img src="https://agentmods.dev/badge/skills/transparent-pegasus/herdrpowers/orchestration.svg" alt="Measured on agentmods" height="20"></a>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.00219 | $0.04803 |
| Opus 5 | $0.00110 | $0.02402 |
| Sonnet 5 | $0.00044 | $0.00961 |
| Haiku 4.5 | $0.00022 | $0.00480 |
Grade A, and why
orchestration 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 8d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration
Configuration resolution
Two files answer "who does what, and which reviews run", in this order:
<repo-root>/.herdrpowers/config.yaml— the target repository's own configuration, written by the init workflow. Wins key by key.roles.yaml— the pack's shipped defaults. Supplies every key the repo file omits.
Read both at the start of every orchestrated task (the repo file may be absent — that is normal, and means defaults apply throughout). They share one schema:
roles:— the role list: each role and the agent type(s) it binds to.fallbacks:— agent → ordered substitutes, for when an agent cannot take work.delegation:— defaults that apply to every task:pane_scope(which panes are eligible at all) andexecution(parallel or serial by default).assignments:— every delegation task, each with the role that performs it.
Merging is per key, not per file: a repo config that sets only assignments.chores.role keeps every other assignment, every role binding, and every fallback at its default.
An assignments: key that roles.yaml does not define is a stale name, not a silent no-op. Name it in the final report so the repo can fix it, because the task it was meant to configure is otherwise running on the shipped default — which would turn a review the repo deliberately disabled back on without saying so. One rename has shipped: plan-double-review became plan-review in v1.10.0. Honor a repo config that still uses the old key as plan-review, and tell the user to rename it.
Customize in the repo file, never in roles.yaml. Plugin installations are read-only, so roles.yaml is not editable there at all; on checked-in copies, editing it makes the pack diff-dirty against upstream. The rest of this skill refers to roles and task names, never to tool names.
If the repo has no .herdrpowers/config.yaml and the user wants to reassign a task, change a mode, or turn a review off, run the init workflow (/herdrpowers:init, or commands/init.md) — do not edit roles.yaml.
What ships with it
3 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.
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.
- 8d ago First seen · 213 lines · 219 tokens per session scan A b04f89237f01
orchestration is a skill published in the GitHub repository transparent-pegasus/herdrpowers (11 stars, last pushed 11d ago), licensed Apache-2.0. It adds 219 tokens to every session and 4,803 once invoked, about $0.0011 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
copperhead
Change or verify a KiCad project through copperhead's gated pipeline. Use whenever a task touches .kicadsch or .kicadpcb files, a schematic, a PCB layout, a netlist, ERC/DRC, a BOM, or hardware design docs — instead of editing those files directly.
grade-and-fix-daedalus
How to grade a Daedalus run (or pasted agent transcript), root-cause the failure, and ship the fix to Daedalus CORE as a stacked PR — without modifying the prompt-vault sandbox (read-only grading). Covers recurring bug archetypes (Unicode punctuation patch mismatch, syntax-vs-type mislabel, emoji box misalignment…
add-slash-command
How to add a new slash command to Daedalus (src/commands), including the docs-sync step that breaks CI if skipped.
merge-aliases
Folds two surface names for the same backend system into one canonical entity, keeping every original mention individually retrievable, and refuses to merge pairs that only share spelling.
anchor-and-lock
Consults a check that sits outside the loop system before finalizing any decision the frozen facts bear on, and refuses every attempt by a loop to rewrite a node marked frozen, regardless of how convergent the loop's own reasoning looks.
counter-metric-check
Compares a watched loop's headline reading against an independently owned counter-metric reading for each period in a governance graph, and produces a governance edge for every period where the counter-metric crosses its recorded ceiling.