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 asherzj/ashers-agent-skills --skill flow-hard-buggit clone --depth 1 https://github.com/asherzj/ashers-agent-skillsWrote 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/asherzj/ashers-agent-skills/flow-hard-bug)<a href="https://agentmods.dev/skills/asherzj/ashers-agent-skills/flow-hard-bug"><img src="https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/flow-hard-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/asherzj/ashers-agent-skills/flow-hard-bug"><img src="https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/flow-hard-bug.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.00541 |
| Opus 5 | $0.00031 | $0.00270 |
| Sonnet 5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
flow-hard-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 9d 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 交付流程
先完整运行 diagnosing-bugs，再使用 implement 完成交付收尾。开始前读取仓库配置、相关领域术语、ADR 和原始 Issue。
范围门禁
先确认用户要求的终点。只要求诊断并不授权修改代码、提交、推送或关闭 Issue；只有用户明确要求修复或交付时才运行完整流程。
流程
- 调用
diagnosing-bugs。在提出理论或修复前，必须先得到一条紧密、可变红、已经实际运行过的反馈命令；随后按其要求完成复现、最小化、排序假设、定向插桩、回归测试、修复和清理。所有展示的命令与产物必须先脱敏。 - 如果无法建立紧密反馈回路，列出尝试过的办法和缺少的产物或权限，然后停止。禁止在没有反馈回路时猜测原因。
- 如果不存在正确的回归测试接缝，记录这个架构发现，不要添加虚假的浅层测试。可把
improve-codebase-architecture作为后续工作，但不要悄悄把 Bug 修复扩大成重构。 - 诊断已经得到验证过的修复并完成清理后，调用
implement作为交付外壳。不要重新诊断或重写修复；只用它核对验收条件、运行聚焦与完整检查、调用code-review、创建工单级提交、推送，并在获授权时关闭事项。
只要求诊断时，在给出证据支持的根因和修复建议后停止，并保存反馈命令供后续修复会话复用。
完成条件
汇报反馈命令、根因、回归覆盖或缺失接缝、原始场景验证、插桩清理、评审结果、提交、远端分支和最终 Issue 状态。仅在本地修好但没有推送，不算交付。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 27 lines · 62 tokens per session scan A 5e4cb62d2a9f
flow-hard-bug is a skill published in the GitHub repository asherzj/ashers-agent-skills (2 stars, last pushed 12d ago), licensed MIT. It adds 62 tokens to every session and 541 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-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.