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-dependency-checkgit 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-dependency-check)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-dependency-check"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-dependency-check/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-dependency-check"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-dependency-check.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.00030 | $0.00669 |
| Opus 5 | $0.00015 | $0.00334 |
| Sonnet 5 | $0.00006 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
yq-dependency-check 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 Dependency Check
Overview
评估三方依赖是否安全、是否过时、升级会带来什么兼容或运维风险，以及是否值得引入。
Core principle: 不只看“能不能装”，还要看“能不能长期安全使用”。
When to Use
- 用户要检查依赖风险、升级影响或漏洞暴露
- 准备升级框架、SDK 或关键基础库
- 想判断一个新依赖是否值得采用
- 线上问题可能与版本漂移、breaking change 或 transitive dependency 有关
Route Elsewhere
- 主要是代码漏洞路径：转
yq-security-scan - 主要是功能异常排查：转
yq-debug - 主要是实现升级代码：转
yq-code-gen
Process
- 识别直接依赖、传递依赖和业务关键程度。
- 检查漏洞、维护状态、发布活跃度和版本跨度。
- 分析 breaking changes、迁移成本和兼容面。
- 评估供应链风险、锁版本策略和回滚方案。
- 输出升级建议、阻塞项和验证重点。
Output
# Dependency Check
## Scope
## Risk Summary
## Vulnerabilities or Drift
## Upgrade Impact
## Compatibility Notes
## Recommendation
## Recommended Next Step
Related Skills
- 常与
yq-security-scan、yq-doc-gen配合 - 涉及代码改造时下游通常接
yq-code-gen - 发版说明可继续交给
yq-git-helper
Recommended Next Step
- 如果依赖风险会扩散到应用攻击面，默认接
yq-security-scan - 如果已经决定升级或替换实现，接
yq-code-gen - 如果需要同步升级说明、验证重点和交付注意事项，补
yq-doc-gen或yq-git-helper
Common Mistakes
- 只看 CVE，不看维护状态和迁移成本
- 忽略传递依赖和锁版本策略
- 升级建议没有验证重点
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 · 89 lines · 30 tokens per session scan A 8a78615d85df
yq-dependency-check is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 669 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…