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 agents/caioniehues/herdmates/issue-trackergit clone --depth 1 https://github.com/caioniehues/herdmatesWrote 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/agents/caioniehues/herdmates/issue-tracker)<a href="https://agentmods.dev/agents/caioniehues/herdmates/issue-tracker"><img src="https://agentmods.dev/badge/agents/caioniehues/herdmates/issue-tracker.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.00000 | $0.00343 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
issue-tracker 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 5d 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
Issue tracker: GitHub Issues
Published 2026-07-15, renamed since: caioniehues/herdmates (public,
marketplace topic herdr-plugin; the original herdr-agent-team slug
survives only as a GitHub redirect — never rely on it). Issues and specs
live on GitHub Issues via the gh CLI.
Conventions
- One issue per ticket;
gh issue create --title "NN — <slug>" --body-file <md>. - Blocking edges as native GitHub blocking links (or a
Blocked by: #Nline in the body where links aren't available). - Triage state via the label vocabulary in
triage-labels.md(needs-triage/needs-info/ready-for-agent/ready-for-human/wontfix). - Specs (PRDs) live in the repo under
docs/; an issue links to its spec section rather than duplicating it. - External PRs ARE a triage surface now — run
/triageover incoming PRs and issues.
History
The v1 build (tickets 01–18) ran on the pre-publish local tracker under
.scratch/team-v1/ (gitignored, retained locally as history). All 18 were
closed before publish; nothing needed migration.
When a skill says "publish to the issue tracker"
gh issue create in this repo.
When a skill says "fetch the relevant ticket"
gh issue view <number> (the user will normally pass the number).
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.
- 5d ago First seen · 34 lines · 0 tokens per session scan A f3cdc99ef6d1
issue-tracker is an agent published in the GitHub repository caioniehues/herdmates (24 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 343 tokens. 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 agents, from other repositories
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
revenue-tracker
OPS specialist: Revenue, billing, and credits analysis agent.
memory-extractor
OPS specialist: Background agent that extracts user profiles, contact cards, and behavioral patterns…
unifly-network-manager
Autonomous UniFi network management agent. Use when the user needs to manage UniFi infrastructure: devices, networks, WiFi, firewall, clients, topology, DHCP reservations, traffic filters, monitoring, or any task involving a UniFi controller. Context: User wants to set up network segmentation user: "Create an IoT VLAN…
ar-producer
OPS specialist: A&R a record like a dance-pop hit label owner + master producer.
Knowledge
Structures codebase exploration into a feature knowledge base and registers it in the index cache.