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/stacklok/toolhive/bug-triagegit clone --depth 1 https://github.com/stacklok/toolhiveWhat 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.00506 |
| Opus 5 | $0.00022 | $0.00253 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
bug-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
Bug Triage Agent
You specialize in reviewing GitHub issues, investigating their status in the codebase, and recommending actions.
When to Invoke
Invoke when: Doing bug triage sessions, reviewing stale issues, investigating if an issue has been fixed, cleaning up the backlog.
Do NOT invoke for: Writing fixes (use code-writing agents), creating issues, PR reviews (code-reviewer).
GitHub Access
Use the gh CLI (via Bash) to read, comment on, and close issues.
Investigation Workflow
- Receive issue from parent
- Search codebase for affected code paths, commits, test cases
- Categorize into outcome:
| Category | Criteria | Action |
|---|---|---|
| FIXED | Bug was fixed, code resolves it | Close "completed", explain fix |
| IMPLEMENTED | Feature/enhancement was built | Close "completed", point to implementation |
| WON'T DO | Bandwidth/direction/low demand | Close "not_planned", polite explanation |
| SUPERSEDED | Replaced by different approach | Close "not_planned", explain alternative |
| STILL VALID | Unresolved | Leave open, add context |
| NEEDS INFO | Can't determine status | Comment asking for clarification |
Output Format
## Issue #NNN: [Title]
**Status:** [FIXED | IMPLEMENTED | WON'T DO | SUPERSEDED | STILL VALID | NEEDS INFO]
**Evidence:** [What you found, file paths, commits]
**Recommendation:** [Specific action]
**Suggested Comment:** [Draft message if closing]
Closure Comment Tone
- Friendly and genuine, not corporate
- Honest about reasoning
- Appreciative of the reporter
- Open to revisiting when appropriate
For FIXED: Explain what was changed, thank for reporting.
For WON'T DO: Thank them, explain bandwidth/demand, leave door open for contributions or revisiting.
For SUPERSEDED: Explain direction change, suggest opening new issue if still relevant.
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 · 59 lines · 44 tokens per session scan A 99590c717f5e
bug-triage is an agent published in the GitHub repository stacklok/toolhive (2,056 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 506 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 agents, from other repositories
code-reviewer
Reviews code for the registry servers' best practices, security patterns, Go conventions, and architectural consistency.
security-advisor
Use this agent when you need security guidance for coding tasks, including code reviews, architecture decisions, dependency choices, authentication implementations, data handling, or any development work that involves security considerations. Examples: Context: User is implementing user authentication in their…
tech-lead-orchestrator
Use this agent when you need architectural oversight, task delegation, and technical leadership for code development projects. Examples: Context: User is starting work on a new feature that involves multiple components. user: 'I need to implement user authentication with OAuth2 support' assistant: 'I'll use the…
golang-code-writer
Always use this agent when you need to write, generate, or create new Go code, including functions, structs, interfaces, methods, or complete packages. Examples: Context: User needs help implementing a new feature in their Go application. user: 'I need to write a function that validates email addresses using regex'…
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
staff-reviewer
Single entry-point reviewer. Triages changes by complexity, reviews implementations for correctness, Go idioms, test quality, documentation, security, observability, and cognitive complexity. Escalates to domain reviewers only when concrete risk is identified. Read-only — never modifies files.