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 firatcand/forge --skill draft-prdgit clone --depth 1 https://github.com/firatcand/forgeWrote 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/firatcand/forge/draft-prd)<a href="https://agentmods.dev/skills/firatcand/forge/draft-prd"><img src="https://agentmods.dev/badge/skills/firatcand/forge/draft-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/firatcand/forge/draft-prd"><img src="https://agentmods.dev/badge/skills/firatcand/forge/draft-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.00043 | $0.00521 |
| Opus 5.5 | $0.00017 | $0.00208 |
| Sonnet 5.5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
draft-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.
What it actually says
/draft-prd
Preconditions
spec/BRIEF.md must exist. If not, refuse and direct the user to /forge.
Orchestration
- Read
spec/BRIEF.md - Check if user has a
product-specskill globally — if yes, invoke it with BRIEF as input - Otherwise, use
templates/PRD.template.mdand walk Claude through filling each section - Per-feature discovery loop — for each item in
BRIEF.v1 scope:- Ask: "What does this feature do? What's the user flow?"
- Ask: "What's the success criteria for this feature? Edge cases or failure modes?"
- Ask: "What does this feature NOT do?" (per-feature non-goals)
- Capture answers as a per-feature subsection in PRD
- Cross-check generated PRD against BRIEF — flag any drift (new features outside v1 scope, definition-of-done that conflicts with BRIEF)
- Write to
spec/PRD.md
Required PRD sections
- Problem (synthesized from BRIEF, made concrete with specific user/moment/workaround)
- Target user (specific persona, JTBD format)
- Per-feature breakdown — for each v1 feature: what it does, user flow, acceptance criteria, edge cases, per-feature non-goals
- Acceptance criteria (overall v1) — testable bullets that prove v1 is done end-to-end
- Non-goals (must include all from BRIEF.non-goals)
- Constraints (budget, timeline, regulatory, integrations, secret management, task tracker)
Output
Print:
PRD written to spec/PRD.md
Per-feature acceptance preview:
- [feature 1]: [criterion]
- [feature 2]: [criterion]
Gate 2 — review the PRD. To proceed:
• /draft-spec to generate the technical SPEC
• /draft-design to generate the DESIGN doc (if UI surface)
• Edit spec/PRD.md directly
• /draft-prd --refine [section] to re-generate a section
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 · 52 lines · 43 tokens per session scan A 30cbd75aa6bc
draft-prd is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 521 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-30.
Other skills, from other repositories
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
design
Set visual and interaction direction for any UI surface (web, React, TUI, CLI, desktop, Qt, design-system tokens) before any UI code. Direction-first: generates 3-4 distinct directions via verbalized sampling, picks one via per-axis single-select, then derives palette, typography, spacing, motion budget. Loads when…
askme
Verbalized Sampling (VS) protocol for intent exploration before planning, mode-aware. Default exhaustive runs full VS; collaborative runs tip-sharing dialogue; adversarial walks the design tree one fork at a time. Auto-detects from phrasing ("help me refine" → collaborative, "poke holes" → adversarial); override via…
grill-me
Adversarial relentless interview against any plan or design until shared understanding is reached. Walk the decision tree, resolve dependencies one answer at a time, recommend a default per question. Trigger when the user says "grill me", "stress-test this", "interview me about this design", or otherwise asks for…
fix
Polymorphic iterative repair loop — accept a verifier failure, structured findings (review/resolve/triage-issue), or a bug description; modify→verify→keep on green, auto-revert on guard regression, until clean or iteration cap. Use when the user says "fix", "make it pass", or "apply the findings", or hands an artifact…
git-branchless
Enforce idiomatic git-branchless during planning and executing tasks — detached-HEAD-first work, in-memory rebase via git move, event-log recovery via git undo, deferred branch creation, speculative-merge git sync for base updates. Use when planning or executing multi-commit work, history rewrites, stack edits…