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-performance-optgit 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-performance-opt)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-performance-opt"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-performance-opt/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-performance-opt"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-performance-opt.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.00028 | $0.00623 |
| Opus 5 | $0.00014 | $0.00311 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
yq-performance-opt 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 Performance Optimization
Overview
定位性能瓶颈，解释证据，提出带权衡说明的优化建议，而不是凭感觉“调快一点”。
Core principle: 先找瓶颈证据，再做优化动作。
When to Use
- 用户反馈慢、吞吐低、资源高、容量不足
- 需要分析慢查询、热点路径、渲染卡顿或批处理耗时
- 需要给出优化优先级和收益预估
- 想避免过早优化或误优化
Route Elsewhere
- 主要是功能 bug：转
yq-debug - 主要是数据库建模：转
yq-db-design - 主要是代码结构清理：转
yq-code-refactor
Process
- 明确性能目标、基线和观测指标。
- 定位最贵的路径、资源和等待点。
- 区分计算、IO、锁、网络、缓存或数据访问瓶颈。
- 给出可验证的优化方案与收益/成本权衡。
- 标出需要监控和回归验证的指标。
Output
# Performance Analysis
## Goal and Baseline
## Bottlenecks
## Evidence
## Optimization Options
## Trade-offs
## Validation Metrics
## Recommended Next Step
Related Skills
- 常与
yq-debug、yq-log-analysis配合 - 结构性优化可继续接
yq-code-refactor - 实施优化时下游通常接
yq-code-gen
Recommended Next Step
- 如果已经确认优化方向，默认接
yq-code-refactor或yq-code-gen落地 - 如果需要把瓶颈证据、指标和优化取舍沉淀下来，补
yq-doc-gen
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 · 87 lines · 28 tokens per session scan A 9429b27bcac8
yq-performance-opt is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 623 once invoked, about $0.0001 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.