Borrowing it
Nothing to install: this file belongs to yi-john-huang/sdd-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yi-john-huang/sdd-mcp/master/.claude/skills/sdd-requirements/SKILL.mdgit clone --depth 1 https://github.com/yi-john-huang/sdd-mcpWrote 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/yi-john-huang/sdd-mcp/sdd-requirements)<a href="https://agentmods.dev/skills/yi-john-huang/sdd-mcp/sdd-requirements"><img src="https://agentmods.dev/badge/skills/yi-john-huang/sdd-mcp/sdd-requirements/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/yi-john-huang/sdd-mcp/sdd-requirements"><img src="https://agentmods.dev/badge/skills/yi-john-huang/sdd-mcp/sdd-requirements.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.00047 | $0.01077 |
| Opus 5 | $0.00023 | $0.00539 |
| Sonnet 5 | $0.00009 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
sdd-requirements 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 11d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Requirements Generation
Generate comprehensive, EARS-formatted requirements documents that integrate with the SDD (Spec-Driven Development) workflow.
Prerequisites
Before generating requirements:
- Feature must be initialized with
sdd-initMCP tool - Check current phase with
sdd-statusMCP tool - Review project steering documents in
.spec/steering/
Workflow
Step 1: Gather Context
- Use
sdd-statusMCP tool to verify feature exists and check current phase - Read project context from
.spec/steering/product.mdif available - Review the feature description from
.spec/specs/{feature}/spec.json
Step 2: Analyze Requirements
Identify and document:
- Primary user goal: What problem are we solving?
- Target users: Who will use this feature?
- Core functionality: What must the system do?
- Success criteria: How do we know it works?
Step 3: Generate EARS-Formatted Requirements
Use the EARS (Easy Approach to Requirements Syntax) format for all requirements.
EARS Patterns
| Pattern | Syntax | Use When |
|---|---|---|
| Ubiquitous | The <system> SHALL <action> |
Always true requirement |
| Event-Driven | WHEN <trigger> THEN the <system> SHALL <action> |
Response to event |
| State-Driven | WHILE <state> THE <system> SHALL <action> |
During specific state |
| Optional | WHERE <feature enabled> THE <system> SHALL <action> |
Configurable feature |
| Unwanted Behavior | IF <condition> THEN the <system> SHALL <action> |
Exception handling |
Examples
## FR-1: User Authentication
WHEN a user submits valid credentials
THEN the system SHALL authenticate the user and return a session token
## FR-2: Session Management
WHILE a user session is active
THE system SHALL maintain the session for up to 24 hours of inactivity
## NFR-1: Performance
The system SHALL respond to authentication requests within 200ms
Step 4: Structure the Document
Generate requirements.md with this structure:
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.
- 11d ago First seen · 148 lines · 47 tokens per session scan A 0b43697e19d0
sdd-requirements is a skill published in the GitHub repository yi-john-huang/sdd-mcp (51 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,077 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…
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…