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 HoangNguyen0403/agent-skills-standard --skill product-requirementsgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/product-requirements)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/product-requirements"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/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/hoangnguyen0403/agent-skills-standard/product-requirements"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/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.00043 | $0.01390 |
| Opus 5.5 | $0.00017 | $0.00556 |
| Sonnet 5.5 | $0.00009 | $0.00278 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Requirements Expert
Priority: P0 (CRITICAL)
Role: PM-owned product spec owner. Define the product "What" before technical design or implementation.
1. Discovery Phase (Iterative)
- Context Injection: Ask for linked BRD objective and business success metric.
- Scope Gate: For substantial scope, load requirements modeling for decomposition stop rules and completeness review; each in-scope leaf maps to a
REQ-*/AC-*or owned gap. - Question Discipline: Draft from supplied evidence; ask at most 3 consequential questions per round (
common-decision-discipline) with recommended defaults and 2–3 concrete options. Never re-ask settled facts.
2. Drafting Phase (System of Record)
- Filesystem: Ensure
docs/prd/exists. Write spec todocs/prd/prd-[slug].mdpreserving slug fromdocs/brd/brd-[slug].md. - Templates & References: Read
references/prd-template.md. Loadreferences/requirements-modeling.mdon-demand for scope trees, decision tables, state/lifecycle, and change impact. - Unknowns Classification: Carry confirmed evidence (
confirmed(<source>)) and explicit non-critical assumptions (assumed(<hypothesis>)). Blocking decisions (blocked(<slice>, <owner>, <input>)) name affected slice, consequence, owner, and required input—no unowned TBD at handoff. - Scope & Traceability: Assign stable
REQ-*andAC-*IDs mapped to BRD objectives. Every in-scope leaf links to REQ/AC or an owned gap (gap(<id>, <owner>, <input>)). Define shared rules/functions canonically once; flows reference by ID/name without duplicate definitions. - User Stories & ACs: Require specific persona, business value, and INVEST check. Use Given/When/Then for one observable behavior per AC across happy, edge, and negative paths; multiple preconditions are permitted. Interacting conditions use truth tables and owner decisions rather than silently selecting policy.
- View Selection: Choose a view that answers the open scope, behavior, or dependency question; use the shared requirements-modeling reference on demand. Diagrams remain optional when prose or tables are precise.
- Implementation Gate & Readiness: Engineering handoff requires behavioral AC, accountable owner, priority, and verification lane per slice. Unverified code routes to
implementation-readiness. Bounded low-risk equivalence (approved ticket with behavioral AC, accountable owner, scope fence, approval, verification lane) satisfies readiness without separate documents; sensitive changes still require technical design and explicit human/governance approval per requirements modeling §1. - Change Impact: When requirements change, trace affected ACs, downstream contracts, approvals, and verification evidence carrying existing IDs without reopening settled decisions.
- Outcome Report: Include
feature_status, requirement trace, completed/missing evidence, decision needed, and recommended next workflow.
What ships with it
5 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 · 83 lines · 43 tokens per session scan A e4ade6545e85
product-requirements is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,390 once invoked, about $0.0002 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-10-16.
Other skills, from other repositories
intelligence-docs
Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
react-idioms
React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance. Use when developing or refactoring React components and client applications. Pair with typescript-idioms.
plan
PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.
coordinate-pro
Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.
coordinate
Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.