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 protect-my-hair/nucleus-marketplace --skill requirement-sizinggit clone --depth 1 https://github.com/protect-my-hair/nucleus-marketplaceWrote 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/protect-my-hair/nucleus-marketplace/requirement-sizing)<a href="https://agentmods.dev/skills/protect-my-hair/nucleus-marketplace/requirement-sizing"><img src="https://agentmods.dev/badge/skills/protect-my-hair/nucleus-marketplace/requirement-sizing/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/protect-my-hair/nucleus-marketplace/requirement-sizing"><img src="https://agentmods.dev/badge/skills/protect-my-hair/nucleus-marketplace/requirement-sizing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01416 |
| Opus 5 | $0.00019 | $0.00708 |
| Sonnet 5 | $0.00008 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
requirement-sizing 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
需求尺寸识别
核心原则
需求尺寸只服务于后续设计规模、设计深度、测试深度和评审强度，不等于工作量、排期或资源承诺。
需求尺寸不得放在 requirement-analysis 开始阶段猜测；不得用一句原始需求、一个标题或早期澄清问题提前判断。
需求尺寸不得换算成人天、story point、sprint 或交付排期。
后续阶段未读取 docs/requirement/<requirementSlug>/evaluation.md 的“需求尺寸”前，不得选择设计模板、设计规模或测试深度。
执行规则
- 在
requirement-analysis后段使用：必须先有澄清、满足度、gap、满足路径、轻量实现口径和工作量评估，再调用requirement-sizing识别需求尺寸。 - 识别时读取 PRD、需求评估、工作量评估、接纳建议和仓库事实；按六个维度逐项判断，取最高风险维度作为尺寸下限。
- 结论写入
.nucleus/runs/<workflowRunId>/requirement-analysis/requirement-sizing.json，并以“尺码-中文规模”写入docs/requirement/<requirementSlug>/evaluation.md的“需求尺寸”章节，例如M-中等规模需求。 - 后续
requirement-design、test-generation-execution和交付收口优先读取evaluation.md的“需求尺寸”。 - 尺寸缺失、低置信、事实变更或与已选方案明显矛盾时，不得静默重算；必须说明缺口或矛盾，并回到需求分析补齐关键事实。
尺寸定义
| 尺寸 | 尺寸定义 | 典型需求 | 设计目标 |
|---|---|---|---|
| XS | 单点变更，业务和技术路径都清楚，低风险 | 文案、字段显示、小规则修正、已有页面轻微调整 | 防止漏边界和验收，不做过度方案化 |
| S | 单一场景或单模块能力，依赖少，有既有模式可套 | 简单列表页、单个配置项、小型状态流转 | 说明场景、接口 / 数据影响、特性归属和验收 |
| M | 多模块协作，有明显方案取舍或数据 / 权限 / 流程影响 | 新后台首页、轻量控制台、一个业务闭环 | 正式需求设计，讲清业务流程、数据流、实现原理、特性拆解、测试规格 |
| L | 跨域、跨产品、跨角色，或架构 / 数据模型 / 权限边界影响明显 | 多产品协作、核心业务流程重构、复杂审批链路 | 深设计，必须有子需求拆分、方案权衡、风险矩阵、回退口径 |
| XL | 战略级或高度未知，无法在一次需求设计中可靠收敛 | 新平台、新业务域、大规模迁移、强不确定 AI 能力 | 不直接产出完整设计，先做 discovery / spike / 拆分计划 |
判定维度
不要按工作量判。按六个维度取最高风险作为尺寸下限。
| 维度 | XS / S | M | L / XL |
|---|---|---|---|
| 业务范围 | 单动作、单场景 | 多场景或一条业务闭环 | 跨业务域 / 跨产品 |
| 方案未知数 | 已有模式 | 有 2-3 个可选方案 | 需调研、验证或拆分 |
| 依赖面 | 无或单依赖 | 多模块依赖 | 多系统、多团队依赖 |
| 数据影响 | 读已有数据 | 新聚合、新状态、新口径 | 新模型、迁移、一致性风险 |
| 权限 / 稳定性 | 基本无影响 | 有权限、降级或异常设计 | 高安全、高稳定性、高审计要求 |
| 评审风险 | 开发自审即可 | 需要技术 / 产品评审 | 需要架构 / 多方评审 |
置信度
- high：关键事实完整，决定性因素有 PRD、评估证据或仓库事实支撑。
- medium：关键事实基本完整，但部分非决定性因素需要后续设计复核。
- low：影响尺寸的关键事实缺失、冲突或仍待人工确认。
low confidence 只能输出阻塞或回补事实建议；不得让需求设计阶段默默重算并继续推进。
人读文案规则
面向用户、PRD、evaluation、设计文档和摘要时使用“需求尺寸”“设计规模”“设计深度”“M-中等规模需求”“采用中等规模设计模板”等人能理解的表达。不得在面向用户的人读文案里直接写内部机器字段名；机器证据可以保留稳定字段。
STOP 规则
- 需求澄清未完成：STOP。
- 满足度、gap、满足路径、轻量实现口径或工作量评估缺失：STOP。
- 需求事实冲突：STOP，回到需求分析补齐。
- 置信度为 low 且没有补充事实：STOP。
- 后续阶段找不到
evaluation.md的“需求尺寸”：STOP，不得从零重新判断并继续下游。 - 尺寸被换算成人天、story point、sprint 或排期：
ALERT_AND_BLOCK。
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 79 lines · 38 tokens per session scan A 6310aedac5df
requirement-sizing is a skill published in the GitHub repository protect-my-hair/nucleus-marketplace (162 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,416 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-08-30.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…