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 The-AI-Directory-Company/agents-and-skills --skill prd-writinggit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/prd-writing)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/prd-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/prd-writing/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/the-ai-directory-company/agents-and-skills/prd-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/prd-writing.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.00024 | $0.01211 |
| Opus 5 | $0.00012 | $0.00606 |
| Sonnet 5 | $0.00005 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
prd-writing 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 9d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Writing
Before you start
Gather the following information. If any is missing, ask the user before proceeding:
- Problem statement — What user pain or business need are we addressing?
- Target users — Which user segments are affected? How many?
- Constraints — Timeline, budget, team size, technical limitations
- Prior art — Has this been attempted before? What happened?
- Stakeholders — Who needs to approve this? Who has opinions?
If the user only gives you a feature idea ("we need dark mode"), push back and ask for the problem ("what user need does dark mode serve?").
PRD template
Use the following template. Every section is required unless explicitly marked optional.
Title
[Feature Name] — Product Requirements Document
1. Problem Statement (2-3 sentences)
State the problem from the user's perspective. Include:
- Who is affected (specific user segment, not "users")
- What they're struggling with (observable behavior, not assumed feelings)
- How severe and frequent the problem is (data if available)
Good: "Enterprise customers with 50+ team members report spending 20+ minutes per week manually reassigning tickets when team members go on PTO, leading to SLA breaches in 12% of cases."
Bad: "Users want better ticket management."
2. Goals & Success Metrics
Define 2-4 measurable outcomes. Each must have:
- A metric name
- A current baseline (if known)
- A target value
- A measurement method
| Metric | Baseline | Target | How to measure |
|---|---|---|---|
| Time to reassign tickets | 20 min/week | < 2 min/week | Avg from activity logs |
| SLA breach rate | 12% | < 3% | Monthly SLA report |
3. User Stories
Write 3-8 user stories in standard format:
As a [user type], I want [action] so that [outcome].
Order by priority. Mark each as P0 (must have), P1 (should have), or P2 (nice to have).
4. Scope
In scope — List specific capabilities included in this work.
What ships with it
2 files 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.
- 9d ago First seen · 134 lines · 24 tokens per session scan A d48b00a29f54
prd-writing is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 1,211 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-09-03.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.