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-view-bugnpx skills add duhuazhu/BugPack --skill bugpack-view-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.00487 |
| Opus 5 | $0.00035 | $0.00244 |
| Sonnet 5 | $0.00014 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
bugpack-view-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 2d 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 - View Bug Details
Fetch full bug context from BugPack, including description, screenshots, environment info, and related files.
Instructions
- Call
GET http://localhost:3456/api/bugs/:idto get the full bug details. - The response includes:
title,description,status,prioritypagePath— the page/route where the bug occursdevice,browser— environment inforelatedFiles— array of file paths related to the bugscreenshots— array of screenshot objects withid,name,original_path,annotated_path
- Display the bug info in a structured format.
- If the bug has screenshots, mention them and offer to show annotated versions.
- If
relatedFilesare listed, use them to locate relevant source code.
Example
GET http://localhost:3456/api/bugs/abc-123
Response:
{
"ok": true,
"data": {
"id": "abc-123",
"title": "Button click not working",
"description": "The submit button on the login page does not respond to clicks",
"status": "open",
"priority": "high",
"pagePath": "/login",
"device": "Desktop",
"browser": "Chrome 120",
"relatedFiles": ["src/pages/Login.tsx", "src/components/SubmitButton.tsx"],
"screenshots": [
{
"id": "ss-001",
"name": "login-bug.png",
"original_path": "/uploads/MyProject/original.png",
"annotated_path": "/uploads/MyProject/annotated.png"
}
]
}
}
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.
- 2d ago First seen · 58 lines · 70 tokens per session scan A 1dc18dc9b141
bugpack-view-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 487 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.