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-system-designgit 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-system-design)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-system-design"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-system-design/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-system-design"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-system-design.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.00706 |
| Opus 5 | $0.00015 | $0.00353 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
yq-system-design 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 System Design
Overview
把需求转成系统级方案，明确组件职责、边界、关键链路、非功能要求和技术取舍。
Core principle: 先定义边界和流转，再讨论技术选型。
When to Use
- 需求基本明确，但实现路径不止一种
- 需要确定模块拆分、调用关系、状态流或部署影响
- 需要把性能、安全、观测、可靠性纳入方案
- 开发前需要统一技术方向和风险控制方式
Route Elsewhere
- 范围和验收标准还不清楚：转
yq-req-analysis - 主要是接口字段与错误语义：转
yq-api-design - 主要是数据库模型：转
yq-db-design - 已经有方案，只差落地：转
yq-code-gen
Process
- 重述目标、约束和本次设计边界。
- 划分组件职责、依赖关系和关键状态。
- 描述主流程、失败流程、恢复或降级路径。
- 说明性能、安全、审计、监控如何落地。
- 对关键方案给出 trade-off、风险和推荐路径。
Output
# System Design
## Goal and Scope
## Assumptions
## Architecture Overview
## Components and Responsibilities
## Key Flows
## Reliability / Security / Observability
## Trade-offs and Alternatives
## Risks
## Recommended Next Step
Related Skills
- 上游通常来自
yq-req-analysis - 下游常接
yq-api-design、yq-db-design、yq-config-gen、yq-code-gen - 复杂多步骤实现前可配合
superpowers:writing-plans
Recommended Next Step
- 默认先交给
yq-api-design、yq-db-design、yq-config-gen细化契约、数据和配置 - 如果方案已经足够具体，也可以直接进入
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.
- 8d ago First seen · 93 lines · 30 tokens per session scan A 02fb8b73e698
yq-system-design 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 706 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…