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 Stijnman/grok-custom-skills --skill product-requirements-documentgit clone --depth 1 https://github.com/Stijnman/grok-custom-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/stijnman/grok-custom-skills/product-requirements-document)<a href="https://agentmods.dev/skills/stijnman/grok-custom-skills/product-requirements-document"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/product-requirements-document/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/stijnman/grok-custom-skills/product-requirements-document"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/product-requirements-document.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.00047 | $0.00463 |
| Opus 5 | $0.00023 | $0.00231 |
| Sonnet 5 | $0.00009 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
product-requirements-document 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.
What it actually says
Product Requirements Document
Purpose
Create a decision-ready product specification that explains why work matters, what must be delivered, what is out of scope, and how success will be evaluated without inventing unavailable facts.
Workflow
- State the user or business problem, relevant context, and the intended outcome.
- Define measurable success criteria and identify the evidence or baseline supporting each one.
- Describe the proposed user-facing behavior and the functional requirements needed to support it.
- Separate in-scope work, explicit exclusions, assumptions, dependencies, and unresolved questions.
- Surface non-functional requirements such as accessibility, reliability, privacy, performance, or security only when relevant.
- Identify risks, owners where known, and validation or rollout considerations.
- Deliver the PRD as a reviewable draft; do not present it as approved unless the user confirms approval.
Required sections
Include: Problem, Goals and success measures, Users and use cases, Scope, Requirements, Non-functional considerations, Dependencies and risks, Open questions, and Acceptance criteria.
Quality boundaries
Do not fabricate customer evidence, market data, timelines, owners, technical commitments, or performance targets. Mark assumptions and placeholders visibly. Keep solution detail sufficient for alignment but leave implementation design to the relevant technical decision process.
Error handling
| Situation | Response |
|---|---|
| Problem is not agreed | Produce a problem-framing draft and identify the missing decision. |
| Requirements conflict | Record the conflict, affected stakeholder, and trade-off rather than hiding it. |
| Metrics have no baseline | Propose a measurement plan and label the target provisional. |
| Scope is too broad | Split the document into a smallest viable release and deferred work. |
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 · 44 lines · 47 tokens per session scan A 71441aed9a40
product-requirements-document is a skill published in the GitHub repository Stijnman/grok-custom-skills (9 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 463 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
goal-meta-skill
A guide for turning an unclear or complex task into a reviewable /goal instruction for coding agents.
workflow-to-skill
Turn a goal and existing CLI, MCP, HTTP, API, or external workflow capabilities into one reviewable reusable Agent Skill. Use when the user asks to create or revise a workflow SKILL.md without a dedicated interface for invocation or result presentation. A webpage, UI, image, or report produced as workflow output does…
rss-digest
Collect RSS or Atom sources and produce a traceable intelligence digest through the configured Weft workflow.
workflow-docs-sync
A project-documentation synchronisation workflow for rebuilding project facts from a local Git folder, GitHub repository, or current working directory, then updating core workflow documents.
workflow-to-skill-with-surface
Create or revise one reusable workflow Skill plus an optional harness-native Prompt Surface that maps a dedicated form, Page, button set, command UI, or result view to ordinary Skill messages and Harness results. Use only when the user explicitly requests a dedicated interface for invoking the Skill or presenting its…
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.