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/prd-templatenpx skills add jsegov/shipspec-claude-code-plugin --skill prd-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/prd-template)<a href="https://agentmods.dev/skills/jsegov/shipspec-claude-code-plugin/prd-template"><img src="https://agentmods.dev/badge/skills/jsegov/shipspec-claude-code-plugin/prd-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.00052 | $0.00994 |
| Opus 5 | $0.00026 | $0.00497 |
| Sonnet 5 | $0.00010 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
prd-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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Template Knowledge
Create well-structured Product Requirements Documents following industry best practices.
Document Structure
A comprehensive PRD includes these sections:
1. Overview (Required)
## 1. Overview
### 1.1 Problem Statement
[2-3 sentences describing the problem users face]
### 1.2 Proposed Solution
[High-level description of what we're building]
### 1.3 Target Users
[Who will use this feature and their characteristics]
### 1.4 Success Metrics
- [Measurable metric 1]
- [Measurable metric 2]
2. Requirements (Required)
Organize requirements with consistent IDs and categories:
## 2. Requirements
### 2.1 Core Features
**REQ-001: [Requirement Title]**
- Description: The system shall [specific, testable behavior]
- Priority: High
- Rationale: [Why this matters]
**REQ-002: [Requirement Title]**
- Description: The system shall [specific, testable behavior]
- Priority: High
- Rationale: [Why this matters]
### 2.2 User Interface
**REQ-010: [UI Requirement]**
- Description: [Specific UI behavior]
- Priority: Medium
### 2.3 Data & Storage
**REQ-020: [Data Requirement]**
- Description: [Data handling behavior]
- Priority: High
Requirement Categories:
- Core Features (REQ-001 to REQ-009)
- User Interface (REQ-010 to REQ-019)
- Data & Storage (REQ-020 to REQ-029)
- Integration (REQ-030 to REQ-039)
- Performance (REQ-040 to REQ-049)
- Security (REQ-050 to REQ-059)
3. User Stories (Required)
## 3. User Stories
### 3.1 Primary Flow
As a [user type], I want to [goal] so that [benefit].
**Acceptance Criteria:**
- Given [context], when [action], then [result]
- Given [context], when [action], then [result]
### 3.2 [Secondary Flow]
As a [user type], I want to [goal] so that [benefit].
4. Technical Considerations (Optional but Recommended)
## 4. Technical Considerations
### 4.1 Constraints
- [Technical constraint 1]
- [Technical constraint 2]
### 4.2 Dependencies
- [Dependency on system X]
- [Dependency on team Y]
### 4.3 Known Technical Debt
- [Relevant existing debt that affects this feature]
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 · 163 lines · 52 tokens per session scan A 5a8f661b20b6
prd-template is a skill published in the GitHub repository jsegov/shipspec-claude-code-plugin (20 stars, last pushed 7mo ago), licensed MIT. It adds 52 tokens to every session and 994 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
ideate
Clarifies a rough idea into a precise problem specification through structured dialogue. Asks targeted questions to surface assumptions, scope, constraints, and actors. Produces a specification document defining WHAT needs to change — not HOW to change it. Use when starting a new feature, brainstorming an idea…
spec-kitty-program-orchestrate
Orchestrate a multi-repo, multi-mission Spec Kitty program end-to-end: run specify → plan → tasks → implement → review → merge → mission-review → post-merge fixes across several repositories in a defined dependency order, using background sub-agents for parallel work and a pulse-heartbeat safety net for long…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
simple-english
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before command, every technical term defined at first use, no AI slop. Default mode is Plain. Strict mode applies full STE…
prd
Generates a Product Requirements Document from a natural language app description. Asks clarifying questions, researches similar apps, defines scope, stack, architecture, and produces a structured PRD that Archon can decompose into a campaign.