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.
git 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/commands/ronronner02/codepilot-agent/spec-prd)<a href="https://agentmods.dev/commands/ronronner02/codepilot-agent/spec-prd"><img src="https://agentmods.dev/badge/commands/ronronner02/codepilot-agent/spec-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/commands/ronronner02/codepilot-agent/spec-prd"><img src="https://agentmods.dev/badge/commands/ronronner02/codepilot-agent/spec-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.00009 | $0.14094 |
| Opus 5.5 | $0.00004 | $0.05638 |
| Sonnet 5.5 | $0.00002 | $0.02819 |
| Haiku 4.5 | $0.00001 | $0.01409 |
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 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command support root: .claude/spec-first/workflows/spec-prd. Treat it as the loaded skill directory whenever this inlined workflow refers to SKILL_DIR or the directory containing SKILL.md.
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.
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 · 343 lines · 9 tokens per session scan A 9a1e81477c4d
spec-prd is a command published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 14,094 once invoked, about $0.0000 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 commands, from other repositories
PyTest.GateKeeper
You are a Senior QA Automation Engineer with deep expertise in Python testing and the pytest framework.
acos
The single command you need. ACOS auto-routes everything.
acos-checkpoint
Create checkpoints before risky operations. Rollback if things go wrong.
attune
AI-powered developer workflows with Socratic discovery.
push
This command will push new design file into the given jira ticket With this command the user will provide arguments.
agent
Create and manage custom AI agents.