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-fix-buggit 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-fix-bug)<a href="https://agentmods.dev/skills/duhuazhu/bugpack/bugpack-fix-bug"><img src="https://agentmods.dev/badge/skills/duhuazhu/bugpack/bugpack-fix-bug/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-fix-bug"><img src="https://agentmods.dev/badge/skills/duhuazhu/bugpack/bugpack-fix-bug.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.00070 | $0.00459 |
| Opus 5.5 | $0.00028 | $0.00184 |
| Sonnet 5.5 | $0.00014 | $0.00092 |
| Haiku 4.5 | $0.00007 | $0.00046 |
Grade A, and why
bugpack-fix-bug 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 - Fix Bug
Read bug context from BugPack, locate the relevant code, apply a fix, and mark the bug as fixed.
Instructions
-
Get bug context: Call
GET http://localhost:3456/api/bugs/:idto fetch full bug details including description, screenshots, environment, and related files. -
Analyze the bug: Read the description and examine the screenshots to understand what is broken and what the expected behavior should be.
-
Locate code: Use the
relatedFilesarray from the bug context to find the relevant source files. IfrelatedFilesis empty, use thepagePathanddescriptionto search the codebase. -
Apply fix: Edit the source code to fix the described issue. Follow the project's existing code style and conventions.
-
Mark as fixed: After applying the fix, call
PATCH http://localhost:3456/api/bugs/:idwith:{ "status": "fixed" } -
Add fix note (optional): Call
PATCH http://localhost:3456/api/bugs/:idwith a description update to document what was changed.
Example
# Step 1: Get bug context
GET http://localhost:3456/api/bugs/abc-123
# Step 5: Mark as fixed
PATCH http://localhost:3456/api/bugs/abc-123
Content-Type: application/json
{ "status": "fixed" }
Response:
{
"ok": true,
"data": {
"id": "abc-123",
"status": "fixed"
}
}
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 · 54 lines · 70 tokens per session scan A 21dfa98b581c
bugpack-fix-bug is a skill published in the GitHub repository duhuazhu/BugPack (34 stars, last pushed 8d ago), licensed MIT. It adds 70 tokens to every session and 459 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
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
chisle-audit
One-shot efficiency audit of a file, diff, or whole repo across BOTH axes at once: over-engineered code (reinvented stdlib, needless abstractions, speculative config) AND bloated prose (verbose comments, padded docstrings, redundant doc sections). Neither a pure code-minimizer nor a pure prose compressor does both in…
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.