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 skills add saajunaid/caddis-plugin --skill prd-to-codegit clone --depth 1 https://github.com/saajunaid/caddis-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/saajunaid/caddis-plugin/prd-to-code)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/prd-to-code"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/prd-to-code/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.
<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/prd-to-code"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/prd-to-code.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00029 | $0.00975 |
| Opus 5.5 | $0.00012 | $0.00390 |
| Sonnet 5.5 | $0.00006 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
prd-to-code 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 19d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD to Code Skill
Transform a Product Requirements Document into a fully functional application.
When to Use
- User provides a PRD document
- User asks to "build from PRD" or "implement this PRD"
- User has requirements to implement
Phase 1: Discovery
- Read the PRD thoroughly
- Extract: data models, API endpoints, UI components, integrations, security requirements
- Interrogate for gaps — do not assume context. Ask about:
- The Core Problem: Why are we building this now?
- Success Metrics: How do we know it worked? (measurable KPIs)
- Constraints: Budget, tech stack, timeline, compliance?
- Ask clarifying questions if needed
PRD Quality Check
Validate that the PRD uses concrete, measurable criteria:
# Vague (BAD) — reject or clarify
- The search should be fast and return relevant results.
- The UI must look modern and be easy to use.
# Concrete (GOOD) — proceed with implementation
+ The search must return results within 200ms for a 10k record dataset.
+ The UI must follow the design system and achieve 100% Lighthouse Accessibility score.
Output: Structured PRD summary with features, models, APIs, components.
Phase 2: Architecture & Scoping
- Create architecture diagram (Mermaid)
- Define project structure
- Plan database schema
- Identify shared libraries to use
- Define Non-Goals — explicitly list what is NOT being built to protect the timeline
- Map User Flows — trace paths through the system for each persona
project/
├── app/ # Frontend
│ ├── pages/
│ ├── components/
│ └── services/
├── backend/ # API layer
│ ├── routers/
│ ├── models/
│ └── services/
└── tests/
Phase 3: Implementation Planning
Break into ordered tasks: Foundation -> Backend -> Frontend -> Integration
Phase 4: Execution
- Set up foundation (structure, config, DB connection)
- Implement backend (models -> repositories -> services -> routers)
- Implement frontend (components -> pages -> integration)
- Apply standards: type hints, logging, parameterized queries, tests
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.
- 19d ago Changed · -3 tokens per session d7878069c661
- 1mo ago First seen · 128 lines · 32 tokens per session scan A f0d5adcf0148
prd-to-code is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 975 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-define-requirements
Define the product requirements that describe what the product must do to deliver the established user experience and achieve the agreed product goals.
goga-discover
Interview the user relentlessly about a decision until every branch of the design tree is resolved, then record the result as a short ADR.