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 agentmods add skills/arezous/pm-pilot/prdnpx skills add arezous/pm-pilot --skill prdgit clone --depth 1 https://github.com/arezous/pm-pilotWhat 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 | $0.00025 | $0.01137 |
| Opus 5 | $0.00013 | $0.00568 |
| Sonnet 5 | $0.00005 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00114 |
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 2d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at writing product requirements documents (PRDs) and feature specifications. You help product managers define what to build, why, and how to measure success.
Source and destination
The skill accepts source material three ways (no hierarchy, all equal):
- Pasted content: Brief, requirements, or feature description pasted directly in the conversation
- File path: A file path dropped into the terminal (starts with
/,~, or./, or ends with a file extension). Read the file automatically. - Workspace reference: A reference to a file in the workspace (e.g., "the search PRD", "the brief in data/"). Find and read it.
If the PM provides an external file path (outside the workspace), read and process it immediately. After processing, offer to save it to data/ for future use.
- Raw input (briefs, stakeholder emails, requirement docs) may live in:
data/ - Output goes to:
output/prd/ - When finalized, specs move to
context/prd/
Workflow
1. Determine the depth
Read template/one-pager.md as the base structure. Every spec starts from this skeleton. Then scale up based on what the PM asked for:
- One-pager ("quick spec", "small feature", "one-pager"): Use the template as-is. 200-400 words. Enough to align on whether to pursue this.
- Brief ("project brief", "brief"): Start from the template, add: scope and constraints (in/out of scope), stakeholders table, open questions. 400-800 words. Enough to kick off a project.
- PRD ("full spec", "detailed spec", "PRD"): Start from the template, add: user stories, prioritized requirements (P0/P1/P2), out of scope, user flow, technical considerations, risks and mitigations, stakeholders. Ask what stage the project is at. A kickoff PRD is 300-500 words (just enough to align the team). A launch-ready PRD is 1500-2000 words (detailed enough to ship). Expand as you learn, not before.
If the phrasing doesn't clearly match a depth, ask the user which fits.
2. Gather evidence
What ships with it
1 file 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.
- 2d ago First seen · 72 lines · 25 tokens per session scan A d900b8d2a1ca
prd is a skill published in the GitHub repository arezous/pm-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 1,137 once invoked, about $0.0001 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-30.
Other skills, from other repositories
etsy-category-listing
Etsy category page scraper: given an Etsy category URL (e.g. https://www.etsy.com/c/jewelry) and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from category and subcategory…
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…
firebase-analytics
Use when logging analytics events, setting user properties, configuring default event parameters, building funnels, or adding screen-view tracking.
firebase-remote-config
Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.
git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…
prismer-evolve-record
Record the outcome of applying an evolution strategy. Use after resolving an error where prismer-evolve-analyze provided a recommendation, to feed back success or failure to the network.