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 danweinerdev/claude-sdd-planner --skill sdd-designgit clone --depth 1 https://github.com/danweinerdev/claude-sdd-plannerWrote 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/danweinerdev/claude-sdd-planner/sdd-design)<a href="https://agentmods.dev/skills/danweinerdev/claude-sdd-planner/sdd-design"><img src="https://agentmods.dev/badge/skills/danweinerdev/claude-sdd-planner/sdd-design.svg" alt="Measured on agentmods" height="20"></a>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.00034 | $0.01537 |
| Opus 5 | $0.00017 | $0.00768 |
| Sonnet 5 | $0.00007 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00154 |
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 3d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Architecture Document
Resources
Before opening shared/..., follow symlinks in this loaded file's path, then derive <plugin-root> from <plugin-root>/skills/<name>/SKILL.md; fallback search roots are repository/user .agents/ (including $HOME/.agents/plugins/*/), Codex ${CODEX_HOME:-$HOME/.codex}/plugins/cache/*/*/*/, and runtime-configured skill roots. Accept only a root containing this skill, shared/agent-runtime.md, and the matching plugin manifest; never use the working directory. Then read <plugin-root>/shared/agent-runtime.md and <plugin-root>/shared/path-resolution.md, and resolve every shared/<path> reference in this skill against <plugin-root>.
Resource boundary: Read the plugin, all SKILL.md files, and shared/ resources in place. Never copy or symlink them into the working directory, target repository, or planning root. Only generated SDD outputs may be materialized from bundled resources.
When to Use
When you need to define the technical architecture for a component or system before implementation. Produces a reviewable design document with architecture decisions.
Process
-
Gather Context
- If the user hasn't already specified it, ask what component to design
- Dispatch a collaboration subagent rendering
shared/agent-prompts/researcher.md(or perform that prompt yourself) with the component and its constraints; it scans all artifact directories and the codebase per its own definition. - Review any related research documents
-
Draft Design
- Create
Designs/<ComponentName>/README.mdusingshared/templates/design.md - Document: overview, non-goals, architecture (components, data flow, interfaces), design decisions (with alternatives considered), error handling, testing strategy, migration plan
- Non-Goals bound the component. Name the responsibilities that belong to neighboring components, the generality this design declines to build, and any extension point deliberately left out. An unstated boundary gets built past
- Where a section realizes a spec requirement, cite its id inline (
FR-NN/NFR-NN—shared/frontmatter-schema.md§ Stable Identifiers) so coverage is greppable - Use Mermaid diagrams for architecture, data flow, and component relationships — prefer
graph TD,flowchart LR, orsequenceDiagramover ASCII art or prose-only descriptions - Testing strategy must include structural verification: Read
shared/language-verification.mdand include the language-appropriate structural checks (sanitizers, static analysis, type checking) in the Testing Strategy section. These define what "structurally correct" means for this component beyond passing tests. - Set status to
draft
- Create
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.
- 3d ago Changed 13f6f8847127
- 7d ago First seen · 68 lines · 34 tokens per session scan A 5d44a492bd0c
sdd-design is a skill published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,537 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-31.
Other skills, from other repositories
moai-platform-chrome-extension
Chrome Extension Manifest V3 development specialist covering service workers, content scripts, message passing, chrome. APIs, side panel, declarativeNetRequest, and Chrome Web Store publishing. Use when building browser extensions.
moai-framework-electron
Electron 33+ desktop app development specialist covering Main/Renderer process architecture, IPC communication, auto-update, and packaging with Electron Forge. Use when building cross-platform desktop applications.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
moai-foundation-context
Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
moai-workflow-jit-docs
Enhanced Just-In-Time document loading system that discovers, loads, and caches relevant documentation based on user intent and project context. Use when users need specific documentation on demand.