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 tomzx/agents --skill write-prdgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/write-prd)<a href="https://agentmods.dev/skills/tomzx/agents/write-prd"><img src="https://agentmods.dev/badge/skills/tomzx/agents/write-prd/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/tomzx/agents/write-prd"><img src="https://agentmods.dev/badge/skills/tomzx/agents/write-prd.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.00030 | $0.00462 |
| Opus 5.5 | $0.00012 | $0.00185 |
| Sonnet 5.5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
write-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 22d 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
Write PRD
The PRD captures what and why, never how.
It states the problem, the desired outcomes, the success criteria tied to goals.md, and the explicit non-goals.
Implementation (architecture, data models, code) belongs to SDLC, not here.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - Strategy gate
proceed:vision.md,goals.md, and the prioritized opportunity.
Steps
- State the problem in one paragraph, drawn from
problems.md. No solutions. - State the desired outcomes (what changes for the customer and the business), tied to objectives in
goals.md. - Define functional requirements (
FR-N): what the product must do to deliver the outcomes, stated as capabilities, not implementations. - Define success criteria: which success metrics (
SM-N) must move, by how much, by when. Referencegoals.md. - State non-goals explicitly: what is deliberately out of scope, to prevent scope creep and set the acceptance boundary.
- List assumptions and open questions that the Define gate or SDLC must resolve.
- Write
prd.mdto the initiative directory.
Output Format
Use the template at skills/pdlc/templates/initiatives/prd.md.
Functional requirements carry FR-N IDs; success criteria reference SM-N IDs from goals.md.
Outcome
If $OUTCOME_YAML is set, emit verdict: drafted.
Completion Checklist
- Problem stated without prescribing a solution
- Outcomes tied to objectives in
goals.md - Functional requirements are capabilities, not implementations
- Success criteria numeric and time-bound
- Non-goals explicit
Next Step
Load prototype-ux (for UI-bearing initiatives) and define-acceptance (the SDLC handoff boundary).
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.
- 22d ago Changed · +5 lines 889563d6163d
- 24d ago Changed f7cd4e3804ed
- 1mo ago First seen · 45 lines · 30 tokens per session scan A 2f662ae30880
write-prd is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 462 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.