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 IceyWu/mcp-hub --skill bug-analysisgit clone --depth 1 https://github.com/IceyWu/mcp-hubWrote 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/iceywu/mcp-hub/bug-analysis)<a href="https://agentmods.dev/skills/iceywu/mcp-hub/bug-analysis"><img src="https://agentmods.dev/badge/skills/iceywu/mcp-hub/bug-analysis.svg" alt="Measured on agentmods" 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.00046 | $0.00449 |
| Opus 5 | $0.00023 | $0.00225 |
| Sonnet 5 | $0.00009 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
bug-analysis 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 6d 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 分析流程
当用户的目标是分析一张表格里的 Bug/问题数据时，按以下步骤进行：
- 定位文档：若用户没给 fileId，用
list_documents（scope=participated）配合 keyword 找到目标 Bug 表，确认 fileId。 - 确认子表：若文档有多个子表，用
list_sheets列出，挑选 Bug 数据所在的子表。不确定时向用户确认。 - 读取数据：用
read_sheet拉取记录。需要全量统计时适当调大maxRecords。
识别字段
Bug 表常见字段（不同表命名可能不同，按语义对应）：
- 状态 / 完成状态：如 待处理、处理中、已解决、已关闭、已验证。
- 优先级 / 严重程度：如 P0/P1/P2、高/中/低、阻塞/严重/一般。
- 负责人 / 指派人。
- 产品分类 / 模块 / 板块。
- 描述 / 标题、创建时间 / 更新时间。
字段名不规范时，根据列名语义做最合理的映射，并在回答中说明你是如何归类的。
统计与呈现
- 统计类问题给出明确数字，例如「共 X 条，未解决 Y 条」。
- 分组统计（按模块/负责人/状态/优先级）用表格清晰呈现，并指出最值（最多/最少）。
- 列出具体 Bug 时，优先展示 标题/描述、状态、优先级、负责人 等关键列。
- 数据为实时读取，不要凭记忆回答；如读取不全（受 maxRecords 限制），如实说明。
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.
- 6d ago First seen · 31 lines · 46 tokens per session scan A 1665fa8b7125
bug-analysis is a skill published in the GitHub repository IceyWu/mcp-hub (0 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 449 once invoked, about $0.0002 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.