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 agentmods add skills/ronronner02/codepilot-agent/spec-prdnpx skills add ronronner02/codepilot-agent --skill spec-prdgit clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/ronronner02/codepilot-agent/spec-prd)<a href="https://agentmods.dev/skills/ronronner02/codepilot-agent/spec-prd"><img src="https://agentmods.dev/badge/skills/ronronner02/codepilot-agent/spec-prd.svg" alt="Measured on agentmods" 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 | $0.00111 | $0.13902 |
| Opus 5 | $0.00056 | $0.06951 |
| Sonnet 5 | $0.00022 | $0.02780 |
| Haiku 4.5 | $0.00011 | $0.01390 |
Grade A, and why
spec-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 yesterday.
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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brownfield PRD Requirements
Purpose
Turn an existing-system increment, rough product note, or low-quality PRD into a standard durable PRD artifact by first thoroughly clarifying requirements with source-first grill-with-docs discipline, then writing WHAT/WHY, current-state evidence, acceptance, scope boundaries, assumptions, and unresolved blockers into the PRD template so spec-plan can plan without inventing product behavior. For existing PRDs, refine diagnoses and rewrites after closure; validate produces a read-only planning-readiness report and never mutates the artifact.
Default-profile mental map: spec-prd is analysis-first: materials become a run-local Requirement Analysis Gate map, the map identifies uncertainty and contradiction points, Product Expert Lens ranks which product/design/technical decisions must be grilled, Requirements Grill closes or carries the load-bearing WHAT gaps, Standard PRD write-in records the decisions, and Readiness Lens asks whether planning or work would still have to invent product behavior. Contract Reset Lite compresses the first three analysis views into one Brief without changing the durable write/readiness spine. Treat either form as a workflow spine, not a direct external skill chain or persistent artifact topology.
Main workflow spine: Input -> Classify / Route Decision -> Input Inventory & Sanitization -> Current-State Evidence -> Requirement Analysis Gate -> Product Expert Lens -> Requirements Grill -> Pre-Write Closure Decision -> PRD Write / Refine -> Readiness Lens + Finalize -> Handoff; validate branches after evidence into Readiness Lens + check-only -> Report, never the write/finalize spine. Treat ready-for-planning, ask-owner, revise-prd, doc-review, and route-out as readiness/handoff outcomes, not the main workflow chain. Treat checkpoint-prd as a write_mode recovery shape under Pre-Write Closure Decision, never as a readiness outcome or planning handoff.
Use the current host/session date when dating PRD requirements documents. If the date is unavailable, read it with a deterministic command; do not hard-code calendar years in this source file. All file references in generated documents must use repo-relative paths.
What ships with it
22 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.
- assets/overlays/securities.md 22 KB
- assets/templates/00-generic.md 15 KB
- assets/templates/10-app.md 3.8 KB
- assets/templates/20-admin.md 3.7 KB
- assets/templates/30-backend.md 3.8 KB
- assets/templates/40-h5-pc.md 2.3 KB
- assets/templates/50-cli-devtool.md 3.4 KB
- assets/templates/60-mixed.md 2.4 KB
- assets/templates/70-large-requirement-index.md 2.2 KB
- references/design-source-evidence.md 8.1 KB
- references/domain-language-and-decision-ledger.md 22 KB
- references/evidence-and-topology.md 15 KB
- references/grill-with-docs-integration.md 12 KB
- references/large-input-checkpoint.md 5.8 KB
- references/prd-output-template.md 48 KB
- references/prd-readiness-lens.md 33 KB
- references/product-analysis-lite.md 8.1 KB
- references/product-expert-lens.md 12 KB
- scripts/check-glossary-drift.js 5.2 KB runs code
- scripts/check-prd-artifact.js 71 KB runs code
- scripts/finalize-prd-artifact.js 17 KB runs code
- scripts/lib/reason-codes.js 4.1 KB runs code
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.
- yesterday First seen · 341 lines · 111 tokens per session scan A 26199b91a9d7
spec-prd is a skill published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 3d ago), licensed MIT. It adds 111 tokens to every session and 13,902 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
setup-vpeetla-skills
Bootstrap a vpeetla-ai repo for org skills: issue tracker, triage labels, docs paths, and CONTEXT.md placement. Use when onboarding a new repo, first clone, or when the user says setup skills or configure agent workflow.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
jelou-workflow
Authoring helpers for Jelou workflow JSON files: create new workflows inside a project via workflow create, discover available targets via workflow list (organization → skills → channels), and validate local workflow files via workflow validate. Use when adding a workflow to an existing project, picking which target…
jelou-project
Manage projects (AI assistants), knowledge files, and channels (messaging integrations) via the Jelou CLI or HTTP API. Use when creating, listing, updating, or deleting projects, uploading knowledge files (PDF, TXT, CSV), viewing project details, managing project knowledge, listing/creating channels for a project…