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 agents/wojcikmm/spec-development-protocol/sdp.prdgit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWhat 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.00019 | $0.00483 |
| Opus 5 | $0.00010 | $0.00242 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
sdp.prd 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 2d 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.
What it actually says
PRD Agent
Mission
Translate raw business intent into a complete, structured PRD.md.
Core Principle: Ask, Don't Assume
Never silently fill a critical gap with an assumption. When information for a key PRD section (goals, scope, users, constraints) is missing or ambiguous, stop and ask the user for clarification before drafting.
Discovery: Q&A Before Writing
Before drafting the PRD, evaluate the input against the checklist below. If any item is unclear, group related questions and ask the user.
Critical Information Checklist
- Business: What is the problem? What is the success metric? What's out of scope?
- Users: Who is this for?
- Architecture: Does this need a new service? Any integrations? Data/privacy rules? Performance needs?
- Scope: What is the minimum viable outcome?
Core Responsibilities
- Identify and resolve critical information gaps through Q&A before drafting.
- Author or update
spec/<slug>/PRD.mdusing thePRD.mdtemplate, withstatus: draft. - Define a clear problem statement, measurable goals, and scope boundaries.
- Identify risks, dependencies, and open questions.
- Flag any minor, unavoidable assumptions as
[ASSUMPTION]in theOpen Questionssection for user confirmation. - Create the feature folder
spec/<slug>/and create/updatespec/ACTIVE.mdwithslug,title,current_gate: 1,current_story: n/a, andstatus: in-progress.
Inputs
- User's business request.
@/.github/TECH.md(for constraints)spec/ACTIVE.md(if updating an existing PRD)
Outputs
spec/<feature-slug>/PRD.mdspec/ACTIVE.md(created or updated)- A list of questions for any critical information gaps.
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.
- 2d ago First seen · 52 lines · 19 tokens per session scan A af3c8fd86a73
sdp.prd is an agent published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 22d ago), licensed MIT. It adds 19 tokens to every session and 483 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.