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 tercel/spec-forge --skill prd-generationgit clone --depth 1 https://github.com/tercel/spec-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/tercel/spec-forge/prd-generation)<a href="https://agentmods.dev/skills/tercel/spec-forge/prd-generation"><img src="https://agentmods.dev/badge/skills/tercel/spec-forge/prd-generation/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/tercel/spec-forge/prd-generation"><img src="https://agentmods.dev/badge/skills/tercel/spec-forge/prd-generation.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.00097 | $0.04139 |
| Opus 5.5 | $0.00039 | $0.01656 |
| Sonnet 5.5 | $0.00019 | $0.00828 |
| Haiku 4.5 | $0.00010 | $0.00414 |
Grade A, and why
prd-generation 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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generation Skill
What Is a PRD?
A Product Requirements Document (PRD) is the central artifact that bridges product strategy and engineering execution. It captures the why, what, and how of a product initiative so that every stakeholder -- from designers and engineers to leadership and QA -- operates from a single source of truth. A well-written PRD reduces ambiguity, prevents scope creep, and provides a measurable framework against which the team can evaluate success.
Within the product development lifecycle a PRD typically sits between the discovery phase (where problems are identified and validated) and the design/engineering phase (where solutions are built). It is not a static document; it evolves through drafts, reviews, and revisions as the team's understanding deepens. This skill treats the PRD as a living document and structures it accordingly.
Five-Step Workflow
Every PRD generated by this skill follows a disciplined five-step process. Each step must be completed before moving to the next.
Step 1 -- Understand Context
Before writing a single line, scan the project to build situational awareness.
@../shared/project-context.md
Execute the Project Context Protocol. Prefer its PC.0 fast path — resolve <sf_scripts> (see @../shared/scripts.md) and run python3 "<sf_scripts>/sf-scan.py" --root "<project_root>", which returns the frameworks and signals (languages, DB/auth signals, test command) plus the existing-doc inventory as documents and document_index (prior PRDs, technical designs, or ADRs with their declared IDs) in one pass. Fall back to the manual PC.1–PC.3 scan only if python3 is unavailable or the script is not found. Use the scan output as the starting inventory, then apply the judgement the script does not:
- Project structure and existing documentation (PC.1)
- Tech stack and framework (PC.2)
- Project profile (PC.3) — Web API, CLI Tool, Frontend, etc.
Additionally:
4. Scan the docs/ directory (if it exists) to find prior PRDs, technical designs, or ADRs. Understanding what has already been decided prevents contradictions and duplicated effort.
5. Identify domain language and team conventions so the PRD speaks the same language as the codebase.
What ships with it
3 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.
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 Changed · +10 lines f840b4e22743
- 1mo ago First seen · 186 lines · 97 tokens per session scan A 1f90c7ccc7f6
prd-generation is a skill published in the GitHub repository tercel/spec-forge (10 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 4,139 once invoked, about $0.0004 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
architecture-diagram
Build interactive, click-through architecture diagrams for software systems — a self-contained single HTML file with animated step-by-step flows, mode toggles (dev/prod, offline/online, v1/v2), dark/light theme, and a side panel with payload details, plus a companion markdown description. Use when the user wants to…
rigorous-review
Rigorous, evidence-backed code review for high-stakes changes. Trigger on: rigorous review, thorough review, deep review, review this PR properly, review before merge, high-stakes review, "is this actually safe to merge", regulated or compliance code review, batch-review these PRs. Every finding carries quoted…
alloy-structural-analysis
Formal model-checking layer over Allium specs using Alloy 6 + Electrod + nuXmv. Trigger on: "rigorous structural analysis", "model-check this spec", "verify this Allium spec formally", "check for structural divergence with Alloy", "run the Alloy loop", "does the code actually satisfy this spec", temporal/CTL/LTL…
daily-briefing
Daily orientation and chief-of-staff briefing. Pulls from Slack (saved items), Gmail (important/starred), Google Calendar (today's events), Jira CLI (configured projects), and Todoist CLI, validates every action item, synthesizes a prioritized briefing using three consequence-based tiers, then produces a decisive…
jira
Manage Jira issues, sprints, and epics via CLI — jira-cli (ankitpokhrel/jira-cli) for bearer/basic-auth instances, acli (Atlassian's official CLI) for OAuth-only Jira Cloud tenants. Trigger on: jira, jira-cli, acli, ticket, issue key (e.g. PROJ-123), work item, epic, sprint, transition/move ticket, comment on ticket…
scala
Use whenever reading, writing, reviewing, or navigating Scala or Java code, or working anywhere in a Scala/Java project (build.sbt, .scala, .java files, sbt/Bloop/BSP setup). Enforces preferred tool order for code search and compile/test, plus house style for collections, sbt workflow, and returns.