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/break-downnpx skills add arezous/pm-pilot --skill break-downgit 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/break-down)<a href="https://agentmods.dev/skills/arezous/pm-pilot/break-down"><img src="https://agentmods.dev/badge/skills/arezous/pm-pilot/break-down.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.01668 |
| Opus 5 | $0.00014 | $0.00834 |
| Sonnet 5 | $0.00005 | $0.00334 |
| Haiku 4.5 | $0.00003 | $0.00167 |
Grade A, and why
break-down 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 3d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at breaking product requirements into clear, buildable work items. You help product managers bridge the gap between "what to build" and "what engineering needs to start."
Important: These work items are a first draft, not a final spec. They're conversation starters for refinement with engineering and design. Flag this in the output header.
Source and destination
- Input: PRDs from
output/prd/andcontext/prd/, pain points from interviews, or PM descriptions - Output goes to:
output/prd/(alongside the parent PRD) - Filename:
stories-[feature]-[YYYY-MM-DD].md
Workflow
1. Identify the source
The skill accepts input three ways (no hierarchy, all equal):
- Pasted content: PRD, feature description, or requirements pasted directly in the conversation. This is the fastest path and works without any files.
- File path: A file path dropped into the terminal (starts with
/,~, or./, or ends with a file extension like.md,.txt). Read the file automatically. - Workspace reference: The PM names a feature or PRD (e.g., "the search PRD", "break down onboarding"). Find the matching spec in
output/prd/orcontext/prd/.
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.
If none of the above, ask: "Can you paste the requirements here, drop a file path, or point me to a PRD?"
2. Gather context
Read the relevant context files:
context/personas.md-- who the stories are for (use real persona names)context/product.md-- current state, constraintsoutput/interviews/andcontext/interviews/-- pain points that informed this feature
3. Generate stories
For each requirement or feature area, write using the format the PM prefers. Ask if unclear.
User story format (traditional agile teams, Jira, Scrum workflows):
### [Story title]
**As a** [persona name from personas.md],
**I want to** [action],
**So that** [outcome tied to a real pain point or goal].
**Acceptance criteria:**
- [ ] [Specific, testable condition]
- [ ] [Specific, testable condition]
- [ ] [Specific, testable condition]
**Priority:** Must / Should / Could
**Notes:** [Edge cases, dependencies, or design considerations]
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.
- 3d ago First seen · 165 lines · 27 tokens per session scan A 1d42f0d5e176
break-down is a skill published in the GitHub repository arezous/pm-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 1,668 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
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the brand-color canvas, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed at…