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-log-analysisgit 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-log-analysis)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-log-analysis"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-log-analysis/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-log-analysis"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-log-analysis.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.00031 | $0.00657 |
| Opus 5 | $0.00015 | $0.00329 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
yq-log-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 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 Log Analysis
Overview
把原始日志转成可读的事件时间线、异常信号和排查线索，减少“看了很多日志但没有结论”的情况。
Core principle: 先提取信号和时间线，再推断根因。
When to Use
- 用户给出大量日志，希望提炼异常点
- 需要按时间线还原请求、任务或事故过程
- 需要从 trace id、request id、错误堆栈里找线索
- 你想先从日志证据收口，再进入 debug
Route Elsewhere
- 主要是代码根因分析：转
yq-debug - 主要是性能基线和瓶颈：转
yq-performance-opt - 主要是安全异常和攻击迹象：转
yq-security-scan
Process
- 识别时间范围、环境、关键请求标识和上下文。
- 去噪并聚合同类错误、告警和状态变化。
- 还原关键时间线和跨模块链路。
- 提取异常模式、首次发生点和重复信号。
- 输出最值得验证的怀疑点和下一步动作。
Output
# Log Analysis
## Scope and Time Window
## Key Signals
## Timeline
## Suspicious Patterns
## Most Likely Failure Points
## Questions to Verify
## Recommended Next Step
Related Skills
- 常作为
yq-debug前置 - 性能侧分析可继续接
yq-performance-opt - 涉及攻击或越权迹象时接
yq-security-scan
Recommended Next Step
- 默认交给
yq-debug，把时间线和异常信号转成根因假设验证 - 如果日志已经明确指向资源瓶颈，改接
yq-performance-opt - 如果日志里出现越权、扫描或异常访问迹象，接
yq-security-scan
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 · 86 lines · 31 tokens per session scan A 581c52dc4f9b
yq-log-analysis is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 657 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.