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-tasks/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-tasks)<a href="https://agentmods.dev/skills/yi-john-huang/sdd-mcp/sdd-tasks"><img src="https://agentmods.dev/badge/skills/yi-john-huang/sdd-mcp/sdd-tasks/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-tasks"><img src="https://agentmods.dev/badge/skills/yi-john-huang/sdd-mcp/sdd-tasks.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.00041 | $0.01793 |
| Opus 5 | $0.00020 | $0.00897 |
| Sonnet 5 | $0.00008 | $0.00359 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
sdd-tasks 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 13d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Task Breakdown Generation
Generate comprehensive TDD-based task breakdowns that translate approved designs into implementable work items.
Prerequisites
Before generating tasks:
- Design must be generated using
/sdd-design - Design phase should be approved (use
sdd-approve designMCP tool) - Review the design document in
.spec/specs/{feature}/design.md
Workflow
Step 1: Verify Prerequisites
Use sdd-status MCP tool to verify:
design.generated: truedesign.approved: true(recommended before tasks)
Step 2: Review Design
- Read
.spec/specs/{feature}/design.md - Identify all components to implement
- Note interfaces and data models
- Understand dependencies between components
Step 3: Apply TDD Workflow
For each task, follow the Red-Green-Refactor cycle:
┌─────────────────────────────────────────────────────────────┐
│ TDD CYCLE │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. RED ──────> Write failing test first │
│ (Test describes expected behavior) │
│ │
│ 2. GREEN ──────> Write minimal code to pass │
│ (Just enough to make test green) │
│ │
│ 3. REFACTOR ────> Clean up, maintain tests passing │
│ (Improve design without breaking) │
│ │
│ ───────────────────────────────────────────────────── │
│ REPEAT │
└─────────────────────────────────────────────────────────────┘
Step 4: Apply Test Pyramid
Structure tests following the 70/20/10 ratio:
╱╲
╱ ╲
╱ E2E╲ 10% - Critical user journeys
╱──────╲
╱ ╲
╱Integration╲ 20% - Component interactions
╱────────────╲
╱ ╲
╱ Unit Tests ╲ 70% - Individual functions
╱──────────────────╲
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.
- 13d ago First seen · 248 lines · 41 tokens per session scan A f2f59de25d8b
sdd-tasks is a skill published in the GitHub repository yi-john-huang/sdd-mcp (52 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,793 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.