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 arezous/pm-pilot --skill prdgit clone --depth 1 https://github.com/arezous/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/arezous/pm-pilot/prd)<a href="https://agentmods.dev/skills/arezous/pm-pilot/prd"><img src="https://agentmods.dev/badge/skills/arezous/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/arezous/pm-pilot/prd"><img src="https://agentmods.dev/badge/skills/arezous/pm-pilot/prd.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.00025 | $0.01137 |
| Opus 5.5 | $0.00010 | $0.00455 |
| Sonnet 5.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 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 — 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.
- 1mo 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 6mo ago), licensed MIT. It adds 25 tokens to every session and 1,137 once invoked, about $0.0001 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
extract-source-sample
Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a source-sample.json in the exact shape the upload-ad-sample skill writes to the Goose Ads library. Also links every character…
create-video-seedance-2-fal
Generate a single 4-15s vertical video clip with ByteDance Seedance 2.0 reference-to-video via fal.ai, for shots with no realistic face (a product hero, a product in motion, an empty set). Multi-image reference (product + setting), ambient audio, internal multi-cut handling within one render, 720p by default. Routes…
comprehensive-enrichment
Enrich any person or company from any identifier — email, name, LinkedIn URL, domain, company name, Twitter/X handle. Use when asked to enrich, look up, or research a lead, contact, person, or company.
meta-ad-manager
Front door and loop owner of a Meta (Facebook/Instagram) ad harness. Reads the brand's ads/ docs, works out which campaign the user means and which stage it is at, hands off to the stage skill that runs it (intake, strategy, creative, launch, checks, fixes, answers), and writes every stage change back to the docs. Use…
google-search-ads-builder
End-to-end Google Search Ads campaign builder. Performs deep keyword research (competitor SEO, review language mining, Reddit/HN community terminology, site audit), builds keyword architecture with funnel mapping and intent classification, creates ad group structure, generates headline/description variants, builds…
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…