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 onatm/agent-skills --skill docs-product-requirementsgit clone --depth 1 https://github.com/onatm/agent-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/onatm/agent-skills/docs-product-requirements)<a href="https://agentmods.dev/skills/onatm/agent-skills/docs-product-requirements"><img src="https://agentmods.dev/badge/skills/onatm/agent-skills/docs-product-requirements/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/onatm/agent-skills/docs-product-requirements"><img src="https://agentmods.dev/badge/skills/onatm/agent-skills/docs-product-requirements.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.00046 | $0.01343 |
| Opus 5 | $0.00023 | $0.00672 |
| Sonnet 5 | $0.00009 | $0.00269 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
docs-product-requirements 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 12d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Product Requirements
Create concise, living PRDs that explain why a product change matters, who it serves, what outcomes and behavior are required, and how success will be evaluated. Keep implementation design and delivery planning in their own documents.
Resource Map
- Use
assets/doc-starters/product-requirements-doc.mdwhen creating or substantially rewriting a PRD. - Read
references/product-requirements-example.mdwhen you need a worked example of the expected evidence and product-level depth.
When to Use
- A new product, initiative, or substantial feature needs product requirements
- An existing PRD needs review, revision, or evidence updates
- Stakeholders need alignment on users, outcomes, scope, requirements, or validation
- A product idea must be shaped before feature design, technical design, or task decomposition
Do Not Use
- Accepted user-visible behavior that belongs in
docs-feature-design - APIs, schema, runtime behavior, deployment, or implementation detail that belongs in
docs-components-design - System topology or cross-component architecture that belongs in
docs-architecture - Strategic sequencing across initiatives that belongs in
docs-product-roadmap - Engineering issue creation that belongs in
linear-task-planning
Workflow
- Identify the artifact and its authority.
- Classify the work as a greenfield product, initiative PRD, feature PRD, revision, or review
- Find existing product strategy, research, analytics, roadmap, feature docs, designs, decisions, and contributor guidance before asking for information already recorded
- Reuse the repository's product-doc location and naming convention; otherwise default to
docs/product/PRD.md - Clarify the audience and decision the PRD must support
- Build an evidence ledger.
- Separate facts, inferences, assumptions, decisions, and unknowns
- Attribute evidence to a source and date; preserve links to interviews, analytics, support signals, market research, and prior decisions
- Treat competitor claims as market context, not proof of customer demand
- Flag stale, conflicting, weak, or segment-mismatched evidence
- Never invent users, quotes, metrics, baselines, deadlines, research, or constraints
What ships with it
3 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.
- 12d ago First seen · 109 lines · 46 tokens per session scan A 2a7f14a57a7a
docs-product-requirements is a skill published in the GitHub repository onatm/agent-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,343 once invoked, about $0.0002 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 skills, from other repositories
nx-monorepo
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx.
turborepo-monorepo
Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…
loom-usage
Meta-orchestration skill for Claude driving loom itself.
curate-collection
Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use…
design-on-call-rotation
Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or…
design-training-program
Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training…