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 skills/duhuazhu/bugpack/bugpack-fix-bugnpx skills add duhuazhu/BugPack --skill bugpack-fix-buggit clone --depth 1 https://github.com/duhuazhu/BugPackWhat 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.00070 | $0.00459 |
| Opus 5 | $0.00035 | $0.00230 |
| Sonnet 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 3d 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.
- 3d 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 (31 stars, last pushed 29d ago), licensed MIT. It adds 70 tokens to every session and 459 once invoked, about $0.0003 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 skills, from other repositories
etsy-category-listing
Etsy category page scraper: given an Etsy category URL (e.g. https://www.etsy.com/c/jewelry) and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from category and subcategory…
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…
firebase-analytics
Use when logging analytics events, setting user properties, configuring default event parameters, building funnels, or adding screen-view tracking.
firebase-remote-config
Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.
git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…
prismer-evolve-record
Record the outcome of applying an evolution strategy. Use after resolving an error where prismer-evolve-analyze provided a recommendation, to feed back success or failure to the network.