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/espennilsen/pi/herdr-setupnpx skills add espennilsen/pi --skill herdr-setupgit clone --depth 1 https://github.com/espennilsen/piWrote 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/espennilsen/pi/herdr-setup)<a href="https://agentmods.dev/skills/espennilsen/pi/herdr-setup"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/herdr-setup.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.00033 | $0.00468 |
| Opus 5 | $0.00016 | $0.00234 |
| Sonnet 5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade C, and why
herdr-setup scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://herdr.dev/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://herdr.dev/install.sh | sh What it actually says
Herdr Setup
Use the installed binary as the source of truth. Do not assume a command or flag from a different version exists.
Inspect first
command -v herdr
herdr --version
herdr --help
herdr integration status
If herdr is absent, explain that it supports Linux and macOS. On Windows, the native preview installer is available; use WSL only if the native preview is unsuitable. Ask before running either upstream installer:
irm https://herdr.dev/install.ps1 | iex
curl -fsSL https://herdr.dev/install.sh | sh
After installation, start a new shell if PATH has not refreshed, then rerun herdr --version.
Integrate Pi
Inspect integration state before changing it:
herdr integration status
Install or update the Pi integration only when requested:
herdr integration install pi
Use herdr integration status --outdated-only to identify stale integrations. Do not remove an integration without confirmation.
Updates and configuration
- Use
herdr updateonly when the user asks to update. - Use
herdr --default-configto inspect defaults before editing configuration. - Treat
HERDR_CONFIG_PATH,HERDR_SESSION, andHERDR_SOCKET_PATHas explicit overrides; report their values before troubleshooting a surprising target/session.
Command or version mismatch
- Stop guessing after an unknown-command or unknown-flag error.
- Run
herdr --help, then<known-group> --helpfor the installed command tree. - Read the upstream docs fallback, selecting the installed release version when available.
- If the installed help and matching version docs disagree, prefer installed help and report the discrepancy.
Safety
herdr server stop, session stop, session delete, and workspace/tab/pane close affect live work. List or inspect state first and ask for confirmation before running them.
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 · 63 lines · 33 tokens per session scan C 282da3a9283b
herdr-setup is a skill published in the GitHub repository espennilsen/pi (117 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 468 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…