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 agentmods add skills/jsegov/shipspec-claude-code-plugin/sdd-templatenpx skills add jsegov/shipspec-claude-code-plugin --skill sdd-templategit clone --depth 1 https://github.com/jsegov/shipspec-claude-code-pluginWrote 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/jsegov/shipspec-claude-code-plugin/sdd-template)<a href="https://agentmods.dev/skills/jsegov/shipspec-claude-code-plugin/sdd-template"><img src="https://agentmods.dev/badge/skills/jsegov/shipspec-claude-code-plugin/sdd-template.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 | $0.00054 | $0.01213 |
| Opus 5 | $0.00027 | $0.00607 |
| Sonnet 5 | $0.00011 | $0.00243 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
sdd-template 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 4d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Design Document Template
Create comprehensive technical design documents following the Atlassian 8-section structure.
Document Structure Overview
| Section | Purpose |
|---|---|
| 1. Introduction | Purpose, scope, definitions |
| 2. System Overview | High-level architecture |
| 3. Design Considerations | Assumptions, constraints, risks |
| 4. Architectural Strategies | Key decisions and alternatives |
| 5. System Architecture | Components, data flow, APIs, models |
| 6. Policies and Tactics | Security, error handling, logging |
| 7. Detailed Design | Component-level specifications |
| 8. Appendix | Diagrams, glossary |
Section Templates
Section 1: Introduction
## 1. Introduction
### 1.1 Purpose
[What this document covers and its intended audience]
### 1.2 Scope
[System boundaries - what's included and excluded]
### 1.3 Definitions and Acronyms
| Term | Definition |
|------|------------|
| [Term] | [Definition] |
### 1.4 References
- PRD: [link to PRD document]
- [Other relevant documents]
Section 2: System Overview
## 2. System Overview
### 2.1 System Context
[How this system fits into the broader architecture]
### 2.2 High-Level Architecture
[Architecture diagram description or ASCII diagram]
### 2.3 Key Components
- **Component A**: [Purpose and responsibility]
- **Component B**: [Purpose and responsibility]
Section 3: Design Considerations
## 3. Design Considerations
### 3.1 Assumptions
- [Assumption 1]
- [Assumption 2]
### 3.2 Constraints
- [Technical constraint]
- [Business constraint]
### 3.3 Dependencies
- [External system X]
- [Library Y version Z]
### 3.4 Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | High/Med/Low | [Strategy] |
Section 4: Architectural Strategies
## 4. Architectural Strategies
### 4.1 Strategy Selection
[Why this architecture was chosen over alternatives]
### 4.2 Alternatives Considered
| Option | Pros | Cons | Decision |
|--------|------|------|----------|
| [Option A] | [Pros] | [Cons] | Selected |
| [Option B] | [Pros] | [Cons] | Rejected |
### 4.3 Key Architectural Decisions
- **Decision 1**: [Decision and rationale]
- **Decision 2**: [Decision and rationale]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 214 lines · 54 tokens per session scan A aefed8bf2cb9
sdd-template is a skill published in the GitHub repository jsegov/shipspec-claude-code-plugin (20 stars, last pushed 7mo ago), licensed MIT. It adds 54 tokens to every session and 1,213 once invoked, about $0.0003 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
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
html-doc
Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render, present, visualize, or make a PRD or design document easier for humans to read in a browser.
create-implementation-plan
Turn a refined requirements document into a structured implementation PLAN.md a fresh session can execute. Planning only — decides the "how", not the "what". Invoke manually only.
refine-ticket
Refine a development ticket — or brainstorm a raw idea — into a validated, self-contained REQUIREMENTS document — the "what", verified against the codebase. Invoke manually only.
bmad-register-skill
Register a custom BMM-dependent skill in the governance registry (bmad/config/bmm-dependencies.csv). Use when the user says "register my skill", "register custom skill", "register bmm dependency", "/bmad-register-skill", or when responding to a convoke-doctor "unregistered-custom-skill" warning with intent to register.
skill-with-manual-entry
Fixture — skill with a frontmatter dep plus a pre-existing manual CSV row (AC9 case 4).