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 skills add duhuazhu/BugPack --skill bugpack-list-bugsgit clone --depth 1 https://github.com/duhuazhu/BugPackWrote 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/skills/duhuazhu/bugpack/bugpack-list-bugs)<a href="https://agentmods.dev/skills/duhuazhu/bugpack/bugpack-list-bugs"><img src="https://agentmods.dev/badge/skills/duhuazhu/bugpack/bugpack-list-bugs/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/skills/duhuazhu/bugpack/bugpack-list-bugs"><img src="https://agentmods.dev/badge/skills/duhuazhu/bugpack/bugpack-list-bugs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00332 |
| Opus 5.5 | $0.00027 | $0.00133 |
| Sonnet 5.5 | $0.00014 | $0.00066 |
| Haiku 4.5 | $0.00007 | $0.00033 |
Grade A, and why
bugpack-list-bugs 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
BugPack - List Bugs
Query the BugPack local server to list all tracked bugs.
Instructions
- Call
GET http://localhost:3456/api/bugsto fetch all bugs.- Optional query param:
?project_id=<id>to filter by project.
- Optional query param:
- Parse the JSON response. Each bug has:
id,title,description,status,priority,project_id,created_at,updated_at. - Present the list in a readable table format, grouped by status (
open/fixed/closed). - If no bugs are found, tell the user there are no tracked bugs.
Example
GET http://localhost:3456/api/bugs
Response:
{
"ok": true,
"data": [
{
"id": "abc-123",
"title": "Button click not working",
"status": "open",
"priority": "high",
"created_at": "2026-03-15T10:00:00Z"
}
]
}
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 · 43 lines · 68 tokens per session scan A 136fb1ef46e9
bugpack-list-bugs is a skill published in the GitHub repository duhuazhu/BugPack (34 stars, last pushed 8d ago), licensed MIT. It adds 68 tokens to every session and 332 once invoked, about $0.0003 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 skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-bug-readiness
Use when assessing a Jira bug ticket for AI autofix readiness. Produces a structured JSON verdict (ready/needsinfo/notfixable) based on a three-gate rubric. Designed for CI pipeline use with the jira-triage orchestrator.
ai-bug-fix-triage
Triage JIRA bugs against repository code to classify AI fixability. Use when reviewing a backlog of bugs to determine which ones an AI agent can fix.
bug-capture
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug"…
plan-dead-code
Configuration-first dead-code audit — Knip baseline for unused files, exports and deps, plus duplication, debug residue, suppression debt, orphan assets, env and schema drift. Emits a ratchet plan; deletes nothing. Use when "find dead code", "is this code used", "unused exports". Apply → housekeep-dead-code.
support-ticket-triage
Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.