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/herdrdev/herdr/triagenpx skills add herdrdev/herdr --skill triagegit clone --depth 1 https://github.com/herdrdev/herdrWhat 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.00053 | $0.00506 |
| Opus 5 | $0.00026 | $0.00253 |
| Sonnet 5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
triage 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 yesterday.
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
Herdr Issue Triage
Use this skill only inside the herdr repository.
When the user says triage, inspect open GitHub issues for herdrdev/herdr and return a concise Markdown table. Prefer GitHub MCP tools when available. If they are unavailable, use gh issue list / gh issue view only when authenticated access is already configured.
Use this table shape:
| Light | Recommendation | Issue | Age | Reactions | Why |
|---|---|---|---|---|---|
| 🔴 | fix now | #123 | 18d | 5 | user-visible regression |
| 🟡 | queue | #124 | 42d | 2 | useful but not blocking |
| 🔵 | defer | #125 | 7d | 0 | cosmetic polish |
Keep issue numbers as Markdown links. Use days since issue creation for Age. Use total reactions for Reactions; include a compact breakdown only when it changes interpretation, such as 7 (5 👍, 2 👀).
Classify with these lights:
- 🔴
fix now: reproducible bug, crash, data loss, blocked workflow, release risk, or high-confidence user-visible regression. - 🟡
queue: useful feature, important quality issue, repeated user signal, stale issue that still looks valid, or behavior worth scheduling. - 🔵
defer: cosmetic polish, low-signal idea, unclear report, docs-only nit, or issue that likely needs more evidence before implementation.
Recommendations should be short imperative phrases: fix now, queue, defer, needs repro, close?, or needs owner decision.
Write one sentence before the table only if needed to state scope, such as how many open issues were inspected. After the table, add at most one short note for uncertainty or follow-up. Do not produce a long narrative unless the user asks for depth.
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.
- yesterday First seen · 31 lines · 53 tokens per session scan A ed743395c18d
triage is a skill published in the GitHub repository herdrdev/herdr (33,954 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 506 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
kungfu-agent-onboarding
Discover the exact Kungfu Project, WorkConsole, WorkRef, Skill catalog, and Core Work state admitted to this Amp process.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
with-frontmatter
Help an agent inspect a failed trace run, identify likely failure layers, and produce a short audit note.
minimal
Help an agent inspect a failed trace run, identify likely failure layers, and produce a short audit note.