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 rockyflux/yq-workflow --skill yq-debuggit clone --depth 1 https://github.com/rockyflux/yq-workflowWrote 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/rockyflux/yq-workflow/yq-debug)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-debug"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-debug/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/rockyflux/yq-workflow/yq-debug"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-debug.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.00038 | $0.00674 |
| Opus 5 | $0.00019 | $0.00337 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
yq-debug 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 8d 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
YQ Debug
Overview
从“现象”走到“根因”和“修复方向”，强调复现、证据链、影响范围和结论可信度。
Core principle: 先找根因，再讨论修复。
When to Use
- 用户要排查问题、定位 bug、解释异常行为
- 测试失败、线上报错、状态不一致或任务执行异常
- 现象存在，但根因不明确
- 需要给出可信的下一步，而不是猜测式修复
Route Elsewhere
- 主要是读懂代码结构：转
yq-code-explain - 已知根因，只差落地修复：转
yq-code-gen - 输入主要是日志集合：先转
yq-log-analysis
Process
- 明确现象、预期差异和触发条件。
- 缩小范围：输入、环境、模块、时间点和最近变更。
- 收集证据：日志、堆栈、状态、配置和复现结果。
- 建立并验证单一假设，区分确认项与高概率怀疑。
- 输出根因、影响范围、修复建议和防回归动作。
Output
# Debug Report
## Symptom
## Trigger Conditions
## Evidence
## Root Cause or Best Hypothesis
## Impact Scope
## Fix Recommendation
## Regression Prevention
## Recommended Next Step
Related Skills
- 常与
yq-log-analysis、yq-code-explain配合 - 下游通常接
yq-code-gen、yq-test-gen - 排障过程建议参考
superpowers:systematic-debugging
Recommended Next Step
- 已确认根因后，默认交给
yq-code-gen落地修复 - 如果需要用测试锁住复现路径和回归风险，接
yq-test-gen - 如果当前证据仍然以日志为主，先补
yq-log-analysis
Common Mistakes
- 一开始就改代码
- 把报错位置误当根因
- 没有区分“已确认”和“待验证”
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.
- 8d ago First seen · 88 lines · 38 tokens per session scan A e663ccfa830e
yq-debug is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 674 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-09-03.
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.