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 vmobifystudio/app-dev-team --skill prd-buildergit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/prd-builder)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/prd-builder"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/prd-builder/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/vmobifystudio/app-dev-team/prd-builder"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/prd-builder.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.00053 | $0.00522 |
| Opus 5.5 | $0.00021 | $0.00209 |
| Sonnet 5.5 | $0.00011 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
prd-builder 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.
What it actually says
PRD builder
Build docs/10-prd.md and docs/11-backlog.md from docs/00-vision.md and docs/01-intake.md.
Required sections (in order)
-
Product summary — 2-3 sentences.
-
Personas — 1-3, each with: name, goal, frustration, context-of-use.
-
User journeys — 3-7 prose paragraphs. Each paragraph: entry → steps → exit → success state.
-
Feature table —
ID Name Description Priority Acceptance criteria Use F-001, F-002, ... Priority is P0/P1/P2.
-
User stories — for each P0 feature, 1–5 stories: As a [persona], I want to [action] so that [outcome] plus Given/When/Then acceptance.
-
Out of scope — explicit list.
-
Open questions — what needs CEO or user input.
Backlog format
docs/11-backlog.md — every backlog item carries both the implementation ticket ID and the PRD feature ID so the chain is traceable end-to-end:
# Backlog
## Sprint 1 — MVP foundation
- APP-001 [F-001] <feature> — XS/S/M/L/XL
- APP-002 [F-002] <feature> — ...
## Sprint 2 — MVP completion
- ...
## v1.1+
- ...
The [F-NNN] is mandatory. The sprint-planner skill carries it through to the board's F-NNN column, and code-reviewer + qa-engineer use it to fetch the matching acceptance criteria from docs/10-prd.md without guessing.
Quality bar
- Every story is buildable by an engineer without another conversation.
- Every acceptance criterion is testable.
- Every P0 traces back to a journey, which traces back to a persona, which traces back to the vision.
If you can't trace a feature back, delete it.
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 · 57 lines · 53 tokens per session scan A 8173d5fbe75a
prd-builder is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 4d ago), licensed MIT. It adds 53 tokens to every session and 522 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-09-03.
Other skills, from other repositories
tower
The front door: a standing conversational session that takes any ask about the repository in plain language, answers questions, and routes work that changes the repository per request onto visual flight (an isolated worker that lands a draft PR) or instrument flight (the spec pipeline), stating its grounds, with…
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
paperclip-distill
Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.