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-security-scangit 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-security-scan)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-security-scan"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-security-scan/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-security-scan"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-security-scan.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.00034 | $0.00636 |
| Opus 5 | $0.00017 | $0.00318 |
| Sonnet 5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
yq-security-scan 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 Security Scan
Overview
从攻击者和防守者视角检查改动中的越权、注入、数据暴露、鉴权缺口和信任边界问题。
Core principle: 先看攻击面和边界，再看实现细节。
When to Use
- 用户要做安全检查、漏洞扫描或上线前安全把关
- 改动涉及认证、授权、敏感数据、文件、网络或第三方输入
- 需要快速识别 release-blocking 风险
- 需要补齐安全视角而不只是功能正确性
Route Elsewhere
- 主要是普通代码质量 review：转
yq-code-review - 主要是依赖版本风险：转
yq-dependency-check - 主要是故障排查：转
yq-debug
Process
- 明确入口、资产、信任边界和攻击面。
- 检查认证、授权、输入校验和输出暴露。
- 检查日志、审计、密钥和敏感配置处理。
- 识别高危利用路径和影响范围。
- 输出优先级明确的修复建议和阻塞项。
Output
# Security Review
## Scope
## Attack Surface
## Findings
## Impact
## Mitigations
## Residual Risks
## Recommended Next Step
Related Skills
- 常与
yq-code-review、yq-dependency-check配合 - 修复安全问题时下游通常接
yq-code-gen - 沉淀上线风险、缓解措施和注意事项时可继续接
yq-doc-gen
Recommended Next Step
- 如果发现可修复的问题，默认交给
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 · 85 lines · 34 tokens per session scan A 7164a3254097
yq-security-scan is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 636 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…