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 wolulabs/hermes-founder-os --skill prd-studiogit clone --depth 1 https://github.com/wolulabs/hermes-founder-osWrote 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/wolulabs/hermes-founder-os/prd-studio)<a href="https://agentmods.dev/skills/wolulabs/hermes-founder-os/prd-studio"><img src="https://agentmods.dev/badge/skills/wolulabs/hermes-founder-os/prd-studio/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/wolulabs/hermes-founder-os/prd-studio"><img src="https://agentmods.dev/badge/skills/wolulabs/hermes-founder-os/prd-studio.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.00061 | $0.00590 |
| Opus 5 | $0.00030 | $0.00295 |
| Sonnet 5 | $0.00012 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
prd-studio 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 9d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Studio
Use this skill after validation confirms an idea is worth defining. PRD Studio converts a validation report or product brief into practical product artifacts for implementation.
The goal is clarity, scope control, and build readiness. Do not reopen market validation unless the provided context is too weak to define an MVP.
Primary Outputs
PRD.mdTASKS.mdUSER_FLOW.mdMVP_CHECKLIST.md
Use This Skill For
- Product requirements.
- MVP scope.
- Feature prioritization.
- User flows.
- Functional requirements.
- Non-functional requirements.
- Non-goals.
- Acceptance criteria.
- Task breakdown.
Do Not Use This Skill For
- Market validation and scoring.
- Architecture review.
- Code implementation.
- UX critique of an existing product.
- Landing page or launch copy.
Default Workflow
- Read the validation report or product brief.
- Extract ICP, problem, promise, constraints, and decision.
- Define MVP objective and riskiest assumption.
- Draft user flows.
- Separate must-have, should-have, later, and explicit non-goals.
- Write functional and non-functional requirements.
- Define acceptance criteria.
- Break work into implementation tasks.
- Produce an MVP checklist.
Scope Rules
- Do not add features outside validated MVP scope.
- Prefer one core workflow over many partial workflows.
- Mark assumptions explicitly.
- Keep non-goals visible.
- Include manual steps when they reduce build risk.
- Use acceptance criteria that can be tested.
- For mobile apps, explicitly classify monetization as digital goods/services, physical goods/services, or external real-world services before specifying payment requirements.
- For iOS/Android apps selling digital content, premium features, credits, or subscriptions consumed in the app, default to platform in-app purchases through Apple IAP and Google Play Billing, often via RevenueCat. Do not specify Stripe, PayPal, Midtrans, or other external payment gateways for those in-app digital purchases unless a documented platform-policy exception applies.
What ships with it
8 files 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.
- examples/PRD.example.md 905 B
- examples/TASKS.example.md 587 B
- examples/USER_FLOW.example.md 522 B
- references/mobile-app-requirements.md 3.8 KB
- references/prd-template.md 1.5 KB
- references/requirements-template.md 1.4 KB
- references/task-breakdown-template.md 698 B
- references/user-flow-template.md 798 B
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.
- 9d ago First seen · 70 lines · 0 tokens per session scan A c217f17d034c
prd-studio is a skill published in the GitHub repository wolulabs/hermes-founder-os (18 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 590 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…