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/initgit 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.00017 | $0.04196 |
| Opus 5 | $0.00009 | $0.02098 |
| Sonnet 5 | $0.00003 | $0.00839 |
| Haiku 4.5 | $0.00002 | $0.00420 |
Grade A, and why
init 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 2d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init Workflow (herdrpowers)
herdrpowers skills and commands reference repo-specific values through <KEY> placeholders (for example <PLAN_PATH_PATTERN>, <BASELINE_VERIFICATION_COMMAND>). This workflow declares the actual values inside the target repository's own instruction files, where every pack file resolves them at runtime. Pack files themselves are never edited: plugin installations are read-only, and checked-in copies stay diff-clean against the pack.
It also writes .herdrpowers/config.yaml: the repository's role list and the role assigned to every delegation task — implementation, tests, chores, verification, and each review. That file is the only place a repo customizes who takes which task and where it runs; skills/orchestration/roles.yaml stays untouched as the shipped default.
Deliverable Saves
This workflow has two deliverables:
- The
Herdrpowers Configurationsection written into the repository's instruction files. .herdrpowers/config.yamlat the repository root — the role list and the per-task role assignments.
Commit both with the repository's normal instruction-file conventions. .herdrpowers/config.yaml is tracked configuration, not scratch — do not add it to .gitignore. (The sibling .herdrpowers/pdd/ workspace ignores itself and is unaffected.)
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.
Execution Steps
- Inventory
Inspect the repository to ground a proposal for every key below: build and test tooling (
package.json,Makefile,pyproject.toml,Cargo.toml, CI workflow files), docs layout, and existingCLAUDE.md/AGENTS.mdcontent. If aHerdrpowers Configurationsection already exists in an instruction file, load it and treat this run as an update of that section. Read the pack'sskills/orchestration/roles.yamlfor the shipped role list, the shippeddelegation:defaults, and the default role assigned to each delegation task. If.herdrpowers/config.yamlalready exists, load it too and treat this run as an update of both deliverables — never silently reset a customized assignment or a gate the user turned off. If herdr is running (HERDR_ENV=1), runherdr pane listand note which agent types actually exist in the session, and which of them share the caller'stab_id. Delegation is confined to the orchestrator's own tab by default, so an agent type that exists only in another tab is not usable by this repository's workflows as configured — flag that, alongside any default assignment naming an agent type this user does not have at all.
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.
- 2d ago First seen · 246 lines · 17 tokens per session scan A 0705dbb83ea5
init is a command published in the GitHub repository transparent-pegasus/herdrpowers (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 17 tokens to every session and 4,196 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
multi-agent-optimize
The Multi-Agent Optimization Tool is an advanced AI-driven framework designed to holistically improve system performance through intelligent, coordinated agent-based optimization. Leveraging cutting-edge AI orchestration techniques, this tool provides a comprehensive approach to performance engineering across multiple…
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
agentlas-connect
Connect Agentlas agents or teams to Telegram.
agentlas-search
Search Agentlas Cloud and Hub agent candidates without invoking.
list-skills
List the Genesis skill catalog (Tier-1 always-indexed + Tier-2 specialized) with a one-line description each, so you can discover under-used capabilities on demand. Optional keyword filter. (Does not list Claude Code plugin skills.).
ask
Consult a craft agent. Routes your question to the best mind in the workshop - not a menu, a recommendation.