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-code-explaingit 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-code-explain)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-code-explain"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-code-explain/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-code-explain"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-code-explain.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.00035 | $0.00668 |
| Opus 5 | $0.00017 | $0.00334 |
| Sonnet 5 | $0.00007 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
yq-code-explain 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 7d 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 Code Explain
Overview
把代码从“能看见”解释成“能理解”，说明职责、主流程、依赖、状态变化和隐含约束。
Core principle: 解释代码时优先回答“它为什么存在、怎样工作、哪里容易踩坑”。
When to Use
- 用户要读代码、解释函数、梳理调用链或快速上手模块
- 需要先理解现状再做修改、排障或评审
- 模块行为复杂，单看代码难以快速形成心智模型
- 需要把实现翻译成更可讨论的业务和工程语言
Route Elsewhere
- 主要是定位故障和根因：转
yq-debug - 主要是交付新代码：转
yq-code-gen - 主要是评审改动风险：转
yq-code-review
Process
- 明确解释目标：函数、模块、链路还是整体架构。
- 提炼入口、出口、关键状态和依赖。
- 说明主流程、分支逻辑和异常处理。
- 标出重要假设、配置点和外部影响。
- 总结最值得关注的风险或修改前提。
Output
# Code Explanation
## Purpose
## Main Flow
## Inputs / Outputs / State
## Dependencies
## Hidden Assumptions
## Risky Areas
## Recommended Next Step
Related Skills
- 作为
yq-debug、yq-code-refactor的常见前置 - 看完代码后准备动手实现时接
yq-code-gen - 需要系统层解读时可回到
yq-system-design
Recommended Next Step
- 如果解释结果暴露了异常路径或怀疑点，默认接
yq-debug - 如果已经明确结构问题，改接
yq-code-refactor - 如果目的只是理解后继续实现，接
yq-code-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.
- 7d ago First seen · 88 lines · 35 tokens per session scan A c3fb19c7e667
yq-code-explain is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 668 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
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
vertical-hr-recruiting
Domain-knowledge primer for the HR & recruiting vertical (ATS, onboarding, workforce scheduling, engagement). Applied by architect/pm during spec authoring so they aren't naive about hiring pipelines, the admitted offer→onboard data-carry gap, EEO/I-9 compliance, and shift-coverage rules. Stops the four products from…
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
vertical-retail
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder…
vertical-fitness
Domain-knowledge pack for fitness & wellness (boutique studios, gyms, coaches, on-demand brands) — the membership vocabulary, non-obvious billing/booking rules, and retention realities a builder must know so fitness products aren't speced naive. Covers the four products this niche ships (class-booking, coaching…