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 agentmods add commands/transparent-pegasus/herdrpowers/executegit clone --depth 1 https://github.com/transparent-pegasus/herdrpowersWhat 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 | $0.00018 | $0.02062 |
| Opus 5 | $0.00009 | $0.01031 |
| Sonnet 5 | $0.00004 | $0.00412 |
| Haiku 4.5 | $0.00002 | $0.00206 |
Grade A, and why
execute 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 yesterday.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/execute Workflow
This command runs the post-plan execution stages of the development cycle. Follow these steps and require user consensus before advancing to the next phase, except between Step 1 and Step 2.
Deliverable Saves
Whenever this workflow saves a deliverable, also save any corresponding design/plan files in the same change so the artifact and its rationale stay together.
Workflow File Edits
Do not edit workflow files unless the user's current request explicitly asks to change a workflow file or workflow behavior. A workflow path alone can select the workflow context; it is not permission to edit that file. For example, update commands/plan.md ... permits editing the workflow, while commands/plan.md add a feature ... to the app does not.
Configuration
<KEY> placeholders in this workflow (for example <PLAN_PATH_PATTERN>) resolve from the Herdrpowers Configuration section of the repository's instruction files (CLAUDE.md / AGENTS.md). If that section is missing, run the pack's init workflow first: /herdrpowers:init on Claude Code plugin installs, or commands/init.md otherwise.
Orchestration
Every dispatch in this workflow goes through the orchestration skill, with using-herdr-sibling-panes as the transport. Read both before the first delegation, and resolve the repository's assignments and review gates as orchestration describes: .herdrpowers/config.yaml first, then orchestration/roles.yaml for anything it omits. Every gate this workflow would run is resolved up front; a gate set to enabled: false is skipped and named in the final report.
Routing comes from assignments:, not from this file, and the resolved YAML is the source of truth for every default — read each task's role and mode there rather than recalling one. This workflow touches complex-coding / simple-coding, test-authoring, fix-round-test-authoring, review-fixes, chores, verification, documentation-impact-review, task-review, fix-round-re-review, and final-branch-review. A review task whose role binds to a list of agent types runs once per entry.
- Plan revisions and final synthesis stay with the orchestrator.
- In-process subagents are not used for workflow work, and the Agent tool is not dispatched for it — with one exception: a review task whose resolved mode is
orchestratorruns in a fresh subagent the orchestrator spawns.
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.
- yesterday First seen · 97 lines · 18 tokens per session scan A c09adbff6397
execute is a command published in the GitHub repository transparent-pegasus/herdrpowers (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 18 tokens to every session and 2,062 once invoked, about $0.0001 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 commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
research-perplexity
Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".