Borrowing it
Nothing to install: this file belongs to luanmorenommaciel/agentspec. 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/luanmorenommaciel/agentspec/main/.claude/skills/sdd-design/SKILL.mdgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/sdd-design)<a href="https://agentmods.dev/skills/luanmorenommaciel/agentspec/sdd-design"><img src="https://agentmods.dev/badge/skills/luanmorenommaciel/agentspec/sdd-design.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.00147 | $0.02803 |
| Opus 5 | $0.00073 | $0.01401 |
| Sonnet 5 | $0.00029 | $0.00561 |
| Haiku 4.5 | $0.00015 | $0.00280 |
Grade A, and why
sdd-design 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 7d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Design — Architecture and Technical Specification (Phase 2)
Transform a validated DEFINE document into a comprehensive DESIGN document: system architecture with diagrams, key decisions with rationale (inline ADRs), an agent-matched file manifest, KB-grounded code patterns, and a testing strategy.
This skill owns the Phase 2 methodology. The design-agent is the executor (identity, tools, boundaries); the /design command is the entrypoint (argument surface and command-only flags). Contract-grade facts — inputs, outputs, status transitions — are canonical in .claude/sdd/architecture/WORKFLOW_CONTRACTS.yaml.
Inputs and Outputs
| Contract | Value |
|---|---|
| Input | .claude/sdd/features/DEFINE_{FEATURE}.md — required sections: problem statement, success criteria, acceptance tests |
| Output | .claude/sdd/features/DESIGN_{FEATURE}.md |
| Artifact shape | .claude/sdd/templates/DESIGN_TEMPLATE.md — the authoritative section structure; follow it, do not invent sections |
| DESIGN status values | Draft → In Progress → Ready for Build (later phases advance it to ✅ Complete (Built), then ✅ Shipped) |
| On completion | DEFINE status → ✅ Complete (Designed) and hand off to /build (Step 7) |
No DEFINE, no design. If requirements are missing or incomplete, stop and route to sdd-define first.
Knowledge Architecture
KB-FIRST RESOLUTION IS MANDATORY, NOT OPTIONAL.
┌─────────────────────────────────────────────────────────────────────┐
│ KNOWLEDGE RESOLUTION ORDER │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ 1. KB PATTERN LOADING (from DEFINE's KB domains) │
│ └─ Read: .claude/kb/{domain}/patterns/*.md → Code patterns │
│ └─ Read: .claude/kb/{domain}/concepts/*.md → Best practices │
│ └─ Read: .claude/kb/{domain}/quick-reference.md → Quick lookup │
│ │
│ 2. AGENT DISCOVERY (for file manifest) │
│ └─ Glob: .claude/agents/**/*.md → Available agents │
│ └─ Extract: Role, capabilities, keywords from each │
│ └─ Match: Files to agents based on purpose │
│ │
│ 3. CONFIDENCE ASSIGNMENT │
│ ├─ KB patterns + agent match found → 0.95 → Design with KB │
│ ├─ KB patterns only → 0.85 → Design, note gaps│
│ ├─ Agent match only → 0.80 → Design, validate │
│ └─ No KB, no agent match → 0.70 → Research first │
│ │
│ 4. MCP VALIDATION (for novel patterns) │
│ └─ MCP docs tool (e.g., context7, ref) → Official docs │
│ └─ MCP search tool (e.g., exa, tavily) → Production examples │
│ │
└─────────────────────────────────────────────────────────────────────┘
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.
- 7d ago First seen · 267 lines · 147 tokens per session scan A 0e41e1141333
sdd-design is a skill published in the GitHub repository luanmorenommaciel/agentspec (246 stars, last pushed today), licensed MIT. It adds 147 tokens to every session and 2,803 once invoked, about $0.0007 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-09-01.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.