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 skills/transparent-pegasus/herdrpowers/update-docsnpx skills add transparent-pegasus/herdrpowers --skill update-docsgit 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/update-docs)<a href="https://agentmods.dev/skills/transparent-pegasus/herdrpowers/update-docs"><img src="https://agentmods.dev/badge/skills/transparent-pegasus/herdrpowers/update-docs.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 | $0.00044 | $0.00259 |
| Opus 5 | $0.00022 | $0.00130 |
| Sonnet 5 | $0.00009 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
update-docs 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 4d 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.
What it actually says
Update Docs
Overview
Keep root-level Markdown docs under docs/ aligned with the current codebase and config.
Use ROOT_DOCS.md in this directory as the contract for what each root doc should contain.
Scope
- Edit only files matching
docs/*.md - Do not edit files inside
docs/*/ - Leave generated or output directories alone, including planning directories, generated content directories, and other paths explicitly marked as outputs by the initialized repository.
Workflow
- Identify which root docs are affected by the change.
- Check
ROOT_DOCS.mdto confirm each affected doc's role and boundaries. - Check the current source of truth in code, config, prompts, schemas, or git history.
- Update only the sections that changed.
- Keep terminology, tone, and structure consistent with the existing file.
- Keep diffs minimal. Prefer surgical edits over rewrites.
- If a doc conflicts with the source of truth, fix the doc.
What ships with it
1 file 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.
- 4d ago First seen · 29 lines · 44 tokens per session scan A 43244c1a3cfa
update-docs is a skill published in the GitHub repository transparent-pegasus/herdrpowers (11 stars, last pushed 7d ago), licensed Apache-2.0. It adds 44 tokens to every session and 259 once invoked, about $0.0002 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
plannotator-tui
Open a Markdown plan or document for the human to review and annotate in a Herdr pane; their feedback arrives as your next message. Use when you have written a plan, spec, or design document that needs human review before you act on it.
compound-v
Use when superpowers:brainstorming is about to begin (pre-brainstorm recon), OR has produced a spec, OR when superpowers:writing-plans has produced a plan, OR when about to invoke superpowers:subagent-driven-development or superpowers:executing-plans. Sidekick that intercepts these four Superpowers transitions — runs…
backend-launcher
Use when Compound V's dispatcher needs to run one file-scoped job on a chosen backend (Claude subagent, headless Codex worker, headless Antigravity worker, headless Cursor worker, headless Devin worker, or headless opencode worker) and get back a canonical jobresult. The single jobspec → jobresult contract every…
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
write-documentation
Use when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.
research-driven-development
Use when the user asks a question about a topic, requests research, or when understanding something is needed before planning. Triggers on "research this", "what is X", "how does Y work", "compare A vs B", "investigate", "deep dive", "look into".