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 stefanoskarakasis/Product-Marketing-Skills --skill prdgit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-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/stefanoskarakasis/product-marketing-skills/prd)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/prd"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/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/stefanoskarakasis/product-marketing-skills/prd"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/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.00056 | $0.04296 |
| Opus 5.5 | $0.00022 | $0.01718 |
| Sonnet 5.5 | $0.00011 | $0.00859 |
| Haiku 4.5 | $0.00006 | $0.00430 |
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 11d 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 — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD — Skill
Guides Product Managers and Product Marketing Managers to co-create complete Product Requirements Documents with embedded Solution Stories. Reads your brain for strategic context.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ PRODUCT REQUIREMENT DOC │
├─────────────────────────────────────────────────────────────────┤
│ STEP 0: Load Brain Context (pre-flight) │
│ ✓ Positioning (Section 3) → Solution Story framing │
│ ✓ ICP (Section 2) → Target customer pre-fill │
│ ✓ Buyer Personas (recent buyer-personas session, if any) → │
│ Stakeholder mapping │
├─────────────────────────────────────────────────────────────────┤
│ STEPS 1-6: Intake → Solution Story → Full PRD → Collaboration │
│ ✓ Conversational intake (role detection) │
│ ✓ Solution Story generation (PMM-first) │
│ ✓ Full PRD structure (10 sections, 2 owners) │
│ ✓ PM + PMM checkpoints (collaboration gates) │
│ ✓ Output format (markdown, copy-paste ready) │
└─────────────────────────────────────────────────────────────────┘
Trigger
- When: User mentions PRD, product requirements, solution story, feature spec, GTM brief, launch plan, product brief, user stories, feature rollout, announcement level, or asks for help structuring a product document.
- Not for: Strategic planning (use
go-to-market-strategy), OKR design (usepmm-okrs), competitive analysis (no dedicated skill yet). - Example prompts:
- "Write a PRD for our new dashboard feature"
- "Help me structure this product initiative"
- "Create a solution story for our messaging team"
- "I have some rough notes — turn them into a PRD"
- "What should we include in the launch section?"
Inputs
- Args: Feature/initiative name, optional existing notes or brief
- Context keys:
/foundation/brain.md— recommended. Sections 2 (ICP), 3 (Alternatives & Positioning)./context/skill-sessions.md— optional; check for a recentbuyer-personassession to pull real committee/persona detail instead of asking from scratch.buyer-personasdoes not write to the brain, so this is a session-log lookup, not a brain section./context/meta-patterns.md— optional; recurring patterns the user has logged from prior PRDs
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.
- 11d ago Changed · -1 lines · +1 tokens per session f4b74f3960a5
- 19d ago Changed 6758e2e1512e
- 24d ago Changed · +1 lines 7769354cac2e
- 25d ago Changed · +13 lines 81380bc8590d
- 1mo ago Changed · +2 lines · -4 tokens per session d468a7afadcd
- 1mo ago Changed · +2 lines 9bbc5374450a
- 2mo ago First seen · 446 lines · 59 tokens per session scan A ceac35ce73a2
prd is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (8 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 4,296 once invoked, about $0.0002 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-31.
Other skills, from other repositories
report
A way to export a chat card or reply as a standalone HTML report, meaning a file that can open in a browser without the chat application. It preserves the card template, including right-to-left Persian or left-to-right English layouts.
k8s-rightsize
Right-size Kubernetes CPU and memory requests from Prometheus usage (p95 CPU, p98 memory over 7 days), size the node count, tune KEDA autoscaling. Use when asked to rightsize workloads, cut node cost, or "how many nodes do we need".
owasp-security
Deep OWASP reference: Top 10 2025, ASVS 5.0, secure patterns, per-language quirks, LLM Top 10 and agentic AI security. Use for an in-depth security review, auth work, or hardening an LLM or agent app. For the everyday baseline use secure-coding.
fig
One self-contained HTML file holding a looping animated SVG, for ideas that move: flows, loops, retries, queues, fan-outs. Use when the user says "fig" or a diagram would be better animated.
brand
A project-specific visual identity for chat cards and saved reports, using the project's colors, logo, and fonts. It finds these details in the repository or asks the user for them, then stores the result in a committable `.readable/` folder.
workspace-rules
A set of guidelines for deciding which rules belong in a repository's workspace instructions and which should be enforced by its build or checks.