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 mshadmanrahman/pm-pilot --skill prdgit clone --depth 1 https://github.com/mshadmanrahman/pm-pilotWrote 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/mshadmanrahman/pm-pilot/prd)<a href="https://agentmods.dev/skills/mshadmanrahman/pm-pilot/prd"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/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/mshadmanrahman/pm-pilot/prd"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.01782 |
| Opus 5.5 | $0.00029 | $0.00713 |
| Sonnet 5.5 | $0.00015 | $0.00356 |
| Haiku 4.5 | $0.00007 | $0.00178 |
Grade A, and why
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 1mo 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD: Product Requirements Document
Generate product specs at the right depth for the decision stage. From a quick one-pager to a full PRD to a technical RFC.
When to Activate
- User says "write a PRD", "product spec", "one-pager for X", "RFC for X"
- User asks for requirements, a spec, or a brief for a feature
- User says "spec this out" or "document the requirements"
Depth Modes
Auto-detect from user phrasing. If ambiguous, ask.
| Mode | When | Length | Contains |
|---|---|---|---|
| One-pager | Early exploration, exec alignment | 1 page | Problem, hypothesis, success criteria, key risks |
| Brief | Ready to start design/discovery | 2-3 pages | Above + user stories, scope (in/out), dependencies |
| Full PRD | Ready to build | 4-8 pages | Above + detailed requirements, edge cases, metrics, rollout plan, open questions |
| RFC | Technical decision needed | 2-5 pages | Context, proposal, alternatives considered, tradeoffs, migration plan |
Detection heuristics
- "quick spec", "one-pager", "executive summary" → One-pager
- "brief", "enough to start building", "design brief" → Brief
- "PRD", "full spec", "detailed requirements" → Full PRD
- "RFC", "tech spec", "architecture decision", "should we migrate" → RFC
Process
Step 1: Gather Context
Before writing, check for existing context:
- Check for market-research output: If competitive analysis exists for this domain, reference it
- Check memory: Look for project context, stakeholder preferences, prior decisions
- Ask the user (if context is thin):
- What problem does this solve?
- Who is it for?
- What does success look like?
- What constraints exist (timeline, team, tech)?
Do not block on missing context. Use what exists, flag what is assumed.
Step 2: Draft
Write the document at the detected depth level, following the templates below.
Tag uncertain claims:
[Assumption]for things you inferred but the user didn't confirm[Needs data]for metrics or claims that need validation[Open question]for decisions that need stakeholder input
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.
- 1mo ago First seen · 268 lines · 73 tokens per session scan A 948bd4ad2cc6
prd is a skill published in the GitHub repository mshadmanrahman/pm-pilot (22 stars, last pushed 23d ago), licensed MIT. It adds 73 tokens to every session and 1,782 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
plan-growth-loop
Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth loops", "prioritize", "what should I build", or "roadmap".
validate-loop
Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".
ops-opnsense
OPNsense configuration via Terraform. Trigger for interfaces, firewall, NAT, DHCP/DNS, aliases.
agent-teams
Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.
dev-auth
Modern web auth implementation (better-auth, NextAuth/Auth.js, Clerk, Supabase Auth; migrating off the deprecated Lucia). Trigger when the user wants to add login, signup, sessions, OAuth, magic links, 2FA, or when existing auth code is detected to audit or migrate.
dev-debug
Systematic debugging - reproduce, isolate the root cause, fix, pin it with a regression test. Use it first whenever the user reports a bug, a crash, an error message, a wrong result or a failing test (a failing CI pipeline is ops-ci-fix), before reading code to guess at the cause.