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.
git 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/commands/transparent-pegasus/herdrpowers/execute_parallel)<a href="https://agentmods.dev/commands/transparent-pegasus/herdrpowers/execute_parallel"><img src="https://agentmods.dev/badge/commands/transparent-pegasus/herdrpowers/execute_parallel/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/commands/transparent-pegasus/herdrpowers/execute_parallel"><img src="https://agentmods.dev/badge/commands/transparent-pegasus/herdrpowers/execute_parallel.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.02920 |
| Opus 5.5 | $0.00007 | $0.01168 |
| Sonnet 5.5 | $0.00003 | $0.00584 |
| Haiku 4.5 | $0.00002 | $0.00292 |
Grade A, and why
execute_parallel 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 1mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/execute_parallel Workflow
This command runs the post-plan execution stages of the development cycle when the approved plan contains tasks that can be implemented safely in parallel. Follow these steps and require user consensus before advancing to the next phase, except between Step 2 and Step 3.
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 implementation tracks (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.
- Track extraction, integration, 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.
- 1mo ago First seen · 141 lines · 17 tokens per session scan A 13fd35a28c0a
execute_parallel is a command published in the GitHub repository transparent-pegasus/herdrpowers (12 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 2,920 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
auto-setup
A command that analyzes a codebase and creates project context documents, including ARCHITECTURE.md and files under .autopus/project.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
speckit.superspec.brainstorm
../../.opencode/commands/speckit.superspec.brainstorm.md.
usually
Prompt Pocket — list your high-frequency prompts and pick one to run; manage your go-to prompts with add/delete/edit/find. Generates a native slash dropdown so you can pick a saved prompt directly.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.