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-evaluationgit 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-evaluation)<a href="https://agentmods.dev/skills/protect-my-hair/nucleus-marketplace/requirement-evaluation"><img src="https://agentmods.dev/badge/skills/protect-my-hair/nucleus-marketplace/requirement-evaluation/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-evaluation"><img src="https://agentmods.dev/badge/skills/protect-my-hair/nucleus-marketplace/requirement-evaluation.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.00033 | $0.00966 |
| Opus 5 | $0.00016 | $0.00483 |
| Sonnet 5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
requirement-evaluation 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.
What it actually says
需求评估
核心原则
没有满足度 gap 和轻量实现口径，不得估工作量。
什么时候使用
当需求分析已经完成关键澄清，需要判断当前产品满足度、接纳成本和工作量可信度时使用。
本 Skill 解决什么
- 当前产品和系统满足度。
- 产品与系统 gap。
- 满足需求需要做哪些事。
- 只服务估算的轻量实现口径。
- 工作量、风险和可信度。
本 Skill 不解决什么
- 不做需求设计。
- 不写正式技术方案。
- 不拆正式特性。
- 不写开发计划或测试计划。
- 不写接口、数据表、权限码或迁移方案。
- 不替产品经理或 PMS 做最终接纳裁决。
执行纪律
必须按顺序完成：
- 读取已澄清需求事实。
- 包括需求目标、背景、用户、场景、首版范围、边界、验收标准和澄清答案。
- STOP：关键澄清未完成时，不得进入评估。
- 读取产品和系统证据。
- 包括产品定位、
docs/features/**、架构文档、实现线索和外部依赖边界。 - STOP：未读产品和系统证据时，不得只凭用户原话估工作量。
- 包括产品定位、
- 写满足度结论。
- 说明当前是 fit、partial-fit、misfit 还是 unknown。
- 说明已有能力能覆盖哪些部分。
- 写 gap。
- gap 必须具体到页面/入口、数据来源、后端支撑、权限、验证、外部依赖等可判断对象。
- STOP：gap 只有“需要开发”“需要确认”这类空话时，不得继续。
- 写满足路径。
- 用产品和工程活动语言说明满足需求需要做哪些事。
- 不写接口、表结构、权限码或任务拆分。
- 写轻量实现口径。
- 只为估算服务，用一句或几句说明技术路径。
- 例如“读取已有调用日志做聚合统计，新增只读控制台入口和权限校验，不接入外部监控栈”。
- 估工作量。
- 每个工作项的依据必须引用 gap、满足路径或轻量实现口径。
- 不能只写 baseline 或“需人工校准”。
工作量纪律
工作量由 agent 根据证据推导，不问用户“工作量是否清楚”“成本项是否清楚”“设计、穿刺、编码、验证、联调是否清楚”。
只有当工作量背后是产品事实或边界选择时，才允许继续澄清，例如：
- 指标必须实时，还是分钟级快照可接受。
- token 统计必须接入计费明细，还是先用已有调用日志。
- 外部监控栈是否纳入首版。
输出要求
输出必须形成一条可读链路：
- 需求澄清结论。
- 当前满足度。
- 产品与系统 gap。
- 满足需求需要做哪些事。
- 轻量实现口径。
- 工作量评估。
- 风险和可信度。
反模式
- 直接从澄清答案跳到人日估算。
- “满足需求需要做哪些事”只有固定模板句。
- 工作量依据只写“基于需求分析 baseline”。
- 用“需要技术设计”替代轻量实现口径。
- 把接口、数据表、权限码、开发任务写进需求评估。
- 让用户确认设计、编码、测试、联调这些成本项是否清楚。
What ships with it
4 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 · 97 lines · 33 tokens per session scan A 1c56ba786595
requirement-evaluation is a skill published in the GitHub repository protect-my-hair/nucleus-marketplace (162 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 966 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…