ToolHive is a platform for running and managing Model Context Protocol servers, which give AI clients access to tools and data. Developers, platform teams, and enterprises use it to isolate MCP servers, control access, and monitor their operation. The catalogue entries provide agent workflows and configuration for operating ToolHive and its MCP servers.
Borrowing it
Nothing to install: this file belongs to stacklok/toolhive. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stacklok/toolhive/main/.claude/agents/bug-triage.mdgit clone --depth 1 https://github.com/stacklok/toolhiveWrote 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/stacklok/toolhive/bug-triage)<a href="https://agentmods.dev/agents/stacklok/toolhive/bug-triage"><img src="https://agentmods.dev/badge/agents/stacklok/toolhive/bug-triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/stacklok/toolhive/bug-triage"><img src="https://agentmods.dev/badge/agents/stacklok/toolhive/bug-triage.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.00506 |
| Opus 5.5 | $0.00018 | $0.00202 |
| Sonnet 5.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 1mo 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
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.
- 1mo ago First seen · 59 lines · 44 tokens per session scan A 99590c717f5e
bug-triage is an agent published in the GitHub repository stacklok/toolhive (2,307 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.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
malware-analyst
Delegates to this agent when the user asks about malware analysis, reverse engineering, binary analysis, disassembly, debugging, sandbox analysis, static analysis, dynamic analysis, or suspicious file triage.
phoenix-bug-fixer
Leads one Phoenix bug from report to draft PR - reproduce, fix, review, revise.
git-investigator
Code archaeology expert. Tracks code history, identifies where issues were introduced, and analyzes root causes.
git-historian
Use this agent for git archaeology, when the user asks "why does this code exist", "when did this break", "what introduced this behavior", mentions "git blame", "git bisect", "pickaxe", "regression", "who changed this", or "find the commit that". Examples.
appsec-run-diagnostician
INTERNAL — dispatched after explicit report-error investigation consent or when APPSECPLUGINDEV=1, either from the offer after a appsec-analyzer run's completion summary or from /appsec-advisor:diagnose-run. Reads the deterministic .run-issues.json, decides per issue whether the symptom is a defect in this plugin or…
qa-lead
The QA Lead owns test strategy, bug triage, release quality gates, and testing process design. Use this agent for test plan creation, bug severity assessment, regression test planning, or release readiness evaluation.