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/simple-task/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/simple-task)<a href="https://agentmods.dev/skills/yi-john-huang/sdd-mcp/simple-task"><img src="https://agentmods.dev/badge/skills/yi-john-huang/sdd-mcp/simple-task.svg" alt="Measured on agentmods" 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.01033 |
| Opus 5 | $0.00019 | $0.00517 |
| Sonnet 5 | $0.00008 | $0.00207 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
simple-task 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simple Task Implementation
Implement small features, bug fixes, or quick enhancements while following best practices from the project's steering documents.
When to Use
Use /simple-task for:
- Small feature additions (e.g., "add logout button")
- Bug fixes
- Minor enhancements
- Quick refactoring
Use full SDD workflow for:
- Complex features requiring multiple components
- New modules or subsystems
- Features needing formal requirements/design review
Workflow
Step 1: Understand the Task
- Clarify what needs to be done
- Identify affected files/components
- Estimate scope (if larger than expected, suggest full SDD workflow)
Step 2: Apply TDD (Test-Driven Development)
Reference: .spec/steering/tdd-guideline.md
Follow the Red-Green-Refactor cycle:
1. RED → Write a failing test first
2. GREEN → Write minimal code to pass
3. REFACTOR → Clean up while tests pass
Quick TDD Checklist:
- Write test before implementation
- Test describes expected behavior
- Minimal code to make test pass
- Refactor without breaking tests
Step 3: Apply Design Principles
Reference: .spec/steering/principles.md
SOLID Quick Reference:
- Single Responsibility: Each function/class does one thing
- Open/Closed: Extend behavior without modifying existing code
- Liskov Substitution: Subtypes must be substitutable
- Interface Segregation: Small, focused interfaces
- Dependency Inversion: Depend on abstractions
Other Principles:
- DRY: Don't repeat yourself - extract common logic
- KISS: Keep it simple - avoid unnecessary complexity
- YAGNI: You aren't gonna need it - only implement what's required
Step 4: Code Quality Review
Reference: .spec/steering/linus-review.md
Before finalizing, ask:
- Taste: Is the solution elegant? Can special cases be eliminated?
- Simplicity: Can it be simpler? Fewer lines? Less nesting?
- Data Structures: Is the right data structure used?
- Breaking Changes: Does this break existing functionality?
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 · 149 lines · 38 tokens per session scan A 9c99da4c3560
simple-task is a skill published in the GitHub repository yi-john-huang/sdd-mcp (51 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,033 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.
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.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
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.