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/plannotator/herdr-annotate/plannotator-tuinpx skills add plannotator/herdr-annotate --skill plannotator-tuigit clone --depth 1 https://github.com/plannotator/herdr-annotateWhat 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.00056 | $0.00457 |
| Opus 5 | $0.00028 | $0.00229 |
| Sonnet 5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
plannotator-tui 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.
What it actually says
plannotator-tui: hand a document to the human for review
Only when HERDR_ENV=1 (you are running inside Herdr). Otherwise tell the human where the
file is and ask them to review it.
-
Write the document to a file. Do not paste it into chat as well.
-
Open it for review, from your own pane:
plannotator-tui herdr open docs/plans/auth.mdplannotator-tui opens beside you (or wherever the user configured it), already knowing that feedback comes back to this pane.
-
End your turn. Do not wait, poll, or read the pane. The review arrives as the next user message, as numbered feedback:
## 1. (line 12) Feedback on: "Rotate the token on every…" > Rotation on every privilege change will log people out…Address every item, then continue.
When you list files you want the human to open, print them as file:// hyperlinks (OSC 8)
so Ctrl-click in Herdr opens them in plannotator-tui:
printf '\e]8;;file://%s\e\\%s\e]8;;\e\\\n' "$PWD/docs/plans/auth.md" "docs/plans/auth.md"
If plannotator-tui is not on PATH, the raw Herdr command is:
herdr plugin pane open --plugin plannotator-tui --entrypoint doc --placement split \
--direction right --target-pane "$HERDR_PANE_ID" --focus --cwd "$PWD" \
--env PLANNOTATOR_TUI_FILE="$PWD/docs/plans/auth.md" --env PLANNOTATOR_TUI_DELIVER_TO="$HERDR_PANE_ID"
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 · 44 lines · 56 tokens per session scan A ca4e167ac3b2
plannotator-tui is a skill published in the GitHub repository plannotator/herdr-annotate (261 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 457 once invoked, about $0.0003 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
tether
Observe and operate durable workloads and reviewed Mission Control groups through Tether's public surfaces without depending on tmux or Herdr internals.
feature-worktree
Before implementing a new feature, isolate it in its own git worktree (own folder + branch) AND its own Herdr pane so parallel sessions never share a checkout or a terminal. Use whenever the user asks to implement, build, add, or work on a new feature, view, panel, or other sizable change to either plugin. Skip for…
herdr-session-parker
Park and resume agent sessions inside Herdr tabs without manually tracking session IDs. Use when the user asks to park a tab/session, resume a parked tab, list parked sessions, free computer resources, hibernate idle agent panes, or manage Herdr Session Parker.
autoreview
Structured Codex, Claude, Amp, Pi, or Kimi code review when explicitly requested.
mira-annotation
Annotate Markdown documents with MIRA research objects and source-local relations. Use for md, smd, qmd, and myst files when identifying claims, evidence, questions, protocols, requests, typed claims, and relation attributes while preserving the original Markdown flavor and author wording. Not for general copyediting…
luvus-module
Write a luvus module (an extension for luvus, mission control for your AI coding agents). Use when the user is building or debugging a luvus module: authoring luvus-module.toml, adding a sidebar dock, Luvus Bar widget, right-click action, event hook, module pane, module settings, or calling luvus back over its UHP.