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-req-analysisgit 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-req-analysis)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-req-analysis"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-req-analysis/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-req-analysis"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-req-analysis.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.00036 | $0.00730 |
| Opus 5 | $0.00018 | $0.00365 |
| Sonnet 5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
yq-req-analysis 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 Requirement Analysis
Overview
把零散想法、口头描述、PRD、Issue 和上下游限制收敛成可设计、可开发、可验收的需求定义。
Core principle: 先澄清目标、边界和验收，再进入设计或编码。
When to Use
- 需求来源很多，但范围和成功标准不清楚
- 用户要梳理功能范围、角色、约束、验收标准
- 团队已经准备设计或开发，但仍有明显歧义
- 你怀疑继续推进会导致返工、范围蔓延或责任不清
Route Elsewhere
- 系统方案和模块边界已成为主要问题：转
yq-system-design - 主要是接口契约：转
yq-api-design - 主要是表结构和迁移：转
yq-db-design - 主要是实现或修 bug：转
yq-code-gen、yq-debug
Process
- 提炼业务目标、用户角色和成功标准。
- 区分事实、假设、约束和待确认项。
- 拆分主流程、异常流程、权限和数据边界。
- 明确范围内、范围外和依赖项。
- 生成可验证的验收标准与开放问题清单。
Output
# Requirement Analysis
## Business Goal
## Users and Scenarios
## In Scope
## Out of Scope
## Constraints and Dependencies
## Acceptance Criteria
## Open Questions
## Recommended Next Step
Related Skills
- 下游通常接
yq-system-design - 细化接口或数据时接
yq-api-design、yq-db-design - 如果需求是多步骤交付输入，可参考
superpowers:writing-plans
Recommended Next Step
- 默认交给
yq-system-design，把目标、边界和验收转成实现方案 - 如果需求已经明确收敛在接口或数据面，也可以直接进入
yq-api-design或yq-db-design
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 · 36 tokens per session scan A 9bd5f0fbfdd2
yq-req-analysis is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 730 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.