agentmods.dev

sdd-init

sdd-init is a skill for Claude Code, Codex from viamus/claude-sdd-plugin. It costs 32 tokens per session (412 once invoked), scanned A, original, MIT.

A command that creates a structured SDD specification file for a component, feature, or module. It starts the project configuration when needed and fills a template with the component name and date.

In plain words
What is it for?
Use it when starting a specification for a new component, feature, or module that should be defined before coding.
Why use it?
It gives a new piece of work a consistent requirements document before implementation begins. It also checks whether a specification with the same name already exists.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the sdd plugin — 8 skills shipped together

not rated 4 4mo ago A scan 32 tokens original MIT
View the source file viamus/claude-sdd-plugin
Install

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.

agentmods
npx agentmods add skills/viamus/claude-sdd-plugin/sdd-init
Any agent
npx skills add viamus/claude-sdd-plugin --skill sdd-init
Clone the repo
git clone --depth 1 https://github.com/viamus/claude-sdd-plugin

Made for: Claude Code, Codex.

Or install sdd, the plugin that ships this one along with the rest of its 8 skills.

Wrote 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.

agentmods badge for sdd-init

README.md
[![agentmods](https://agentmods.dev/badge/skills/viamus/claude-sdd-plugin/sdd-init.svg)](https://agentmods.dev/skills/viamus/claude-sdd-plugin/sdd-init)
Your own site
<a href="https://agentmods.dev/skills/viamus/claude-sdd-plugin/sdd-init"><img src="https://agentmods.dev/badge/skills/viamus/claude-sdd-plugin/sdd-init.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 412 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00412
Opus 5 $0.00016 $0.00206
Sonnet 5 $0.00006 $0.00082
Haiku 4.5 $0.00003 $0.00041

Measured 5d ago against content hash f0e1198d5830, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

sdd-init 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 5d 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.

skills/sdd-init/SKILL.md · 40 lines

What it actually says

SDD Init — Create New Specification

You are the SDD Orchestrator initializing a new specification.

Instructions

  1. The component name is: $ARGUMENTS
  2. If no name was provided, ask the user: "What is the name of the component you want to specify?"
  3. Create the directory specs/ in the project root if it doesn't exist
  4. If sdd.config.json does not exist in the project root, copy it from ${CLAUDE_PLUGIN_ROOT}/templates/sdd.config.json — this gives the user default audit configuration they can customize
  5. Check if specs/$ARGUMENTS.spec.md already exists
    • If it exists, ask: "The spec '$ARGUMENTS' already exists. Do you want to overwrite it?"
  6. Read the template from ${CLAUDE_PLUGIN_ROOT}/templates/spec-template.md
  7. Create the file specs/$ARGUMENTS.spec.md replacing:
    • {component-name} with the argument value (lowercase, kebab-case)
    • {Component Name} with the argument value (Title Case)
    • {date} with today's date (YYYY-MM-DD)
  8. Display this message:
✅ Spec created: specs/$ARGUMENTS.spec.md

Next steps:
  /sdd:sdd-build $ARGUMENTS  → Build the spec through a guided conversation (recommended)
  Edit manually               → Fill in specs/$ARGUMENTS.spec.md directly
  /sdd:sdd-review             → Validate when it's ready

Rules

  • NEVER generate implementation code during this step
  • ONLY create the spec file
  • The spec must start with status: draft
Changes

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.

  1. 5d ago First seen · 40 lines · 32 tokens per session scan A f0e1198d5830

Subscribe to this mod's changes

sdd-init is a skill published in the GitHub repository viamus/claude-sdd-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 412 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.

Code GenerationPlanningWriting and docsai-toolsclaude-codeclaude-code-pluginsddspec-driven-design
Related

Other skills, from other repositories

context

Reqordのデータモデル（Requirement, Specification, ProjectContext, Feedback）とCLI操作ルールの共通知識ベース。.

kicchann/reqord · 30 tokens

feedback

Skill "feedback" from kicchann/reqord, covering scope, feedback運用コマンド, 引数解析, step 1: 同期 and step 1.5: リポジトリ確認.

kicchann/reqord · 52 tokens

setup

Reqordプラグインの環境セットアップと前提条件チェック。CLIツール・GitHub認証・プロジェクト初期化状態を確認し、証憑を記録する。.

kicchann/reqord · 47 tokens

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…

kicchann/reqord · 67 tokens

brief

Skill "brief" from kicchann/reqord, covering scope, コンテキスト一括表示, step 0: 引数解析, step 1a: spec詳細モード and グループa（並列実行）.

kicchann/reqord · 33 tokens

status

Reqordの要件・仕様の実装進捗ダッシュボードを表示する。ステータス別集計、design.md準備状況、未解決フィードバックを一覧表示する。.

kicchann/reqord · 48 tokens