agentmods.dev

sdd-spec

sdd-spec is a skill for Claude Code from 3062-in-zamud/knowledgine. It costs 48 tokens per session (864 once invoked), scanned A, original, MIT.

A guided tool for creating or improving three specification files: requirements, design, and tasks. It examines the codebase and asks questions before producing instructions an AI agent can implement.

In plain words
What is it for?
Use it for writing requirements, documenting technical design, defining implementation tasks, checking affected code areas, and refining an existing specification.
Why use it?
It turns an unclear feature request into consistent, detailed implementation instructions. It also helps update specifications when requirements change.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions AGENTS.md.

not rated 3repo 1mo ago A scan 48 tokens original MIT

Good fit Use it for writing requirements, documenting technical design, defining implementation tasks, checking affected code areas, and refining an existing specification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/3062-in-zamud/knowledgine/sdd-spec
View source ↗ 3062-in-zamud/knowledgine
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.

Any agent
npx skills add 3062-in-zamud/knowledgine --skill sdd-spec
Clone the repo
git clone --depth 1 https://github.com/3062-in-zamud/knowledgine

Made for: Claude Code.

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-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-spec/github.svg)](https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-spec)
Your own site
<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-spec"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-spec/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.

agentmods 80×15 button for sdd-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-spec"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 864 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00048 $0.00864
Opus 5 $0.00024 $0.00432
Sonnet 5 $0.00010 $0.00173
Haiku 4.5 $0.00005 $0.00086

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

Security

Grade A, and why

sdd-spec 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 11d 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.

.ai-agents/skills/sdd-spec/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sdd-spec

Purpose

Write high-quality specifications that AI agents can follow to implement features correctly. This skill guides the creation of all three spec files in sequence, ensuring they are internally consistent and actionable.

When to Use

  • After /sdd-init has created the spec directory with templates
  • To refine or update an existing spec that needs improvement
  • When requirements have changed and the spec needs updating

Arguments

  • $ARGUMENTS: Spec ID (e.g., KNOW-001) or path to spec directory

Step-by-Step Instructions

Phase 1: Analyze Context

  1. Read the spec directory to see what's already written
  2. Run /sdd-analyze (or equivalent analysis) on affected packages:
    • Current architecture patterns
    • Public APIs that will be touched
    • Existing test coverage
    • Related past knowledge via knowledgine-recall
  3. Identify affected packages from the template checklist

Phase 2: Requirements (requirements.md)

  1. Dialogue with the user to understand:

    • What problem does this solve? Who is affected?
    • What does "done" look like? (acceptance criteria)
    • What are the constraints? (performance, compatibility, security)
    • What is explicitly out of scope?

  2. Write acceptance criteria that are:

    • Testable: Each criterion maps to a concrete test
    • Specific: No vague terms like "should work well"
    • Complete: Cover happy path, error cases, edge cases

  3. Update requirements.md with:

    • Problem Statement
    • Acceptance Criteria (all checkboxes)
    • Constraints
    • Affected Packages (checked)
    • Out of Scope
    • Status: draft

Phase 3: Design (design.md)

  1. Based on requirements + code analysis, design the solution:

    • Architecture Overview (how it fits into existing system)
    • Interface Definitions (TypeScript types/interfaces)
    • Data Flow (step-by-step)
    • Key Design Decisions (with alternatives and rationale)

  2. Validate that:

    • Every acceptance criterion is addressed by the design
    • Interfaces follow existing patterns in the codebase
    • Data flow is complete (no gaps)

Read the full file on GitHub · 111 lines

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. 11d ago First seen · 111 lines · 48 tokens per session scan A a9258aa97e4c

Subscribe to this mod's changes

sdd-spec is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 864 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.

PlanningWriting and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens