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 racecraft-lab/racecraft-plugins-public --skill speckit-prdgit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/racecraft-lab/racecraft-plugins-public/speckit-prd)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-prd"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-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/racecraft-lab/racecraft-plugins-public/speckit-prd"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00164 | $0.01051 |
| Opus 5 | $0.00082 | $0.00526 |
| Sonnet 5 | $0.00033 | $0.00210 |
| Haiku 4.5 | $0.00016 | $0.00105 |
Grade A, and why
speckit-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 today.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit PRD
Create or update three consistent Markdown artifacts: a lean PRD for WHAT and WHY, a technical roadmap whose SPEC catalog maps 1:1 to PRD Features, and a roadmap-MOC that makes the spec tree navigable.
Ground recommendations
Inspect the tools and skills actually available. Follow the shared
capability-discovery
and grounding contracts.
Read applicable project instructions, .specify/memory/constitution.md, prior
roadmaps and decisions, and targeted code. Disclose uncertainty; do not guess.
Codex interaction adapter
In an active user chat, prefer request_user_input whenever it is present. Send
one question at a time with 2-3 mutually exclusive choices: put the grounded
recommendation first, suffix its label (Recommended), and state each tradeoff
briefly. Wait for the user's reply before the next question.
If the picker is absent or its call is unavailable, use a free-text fallback only in the already active user chat. Ask exactly one question, list the recommended choice first plus 1-2 mutually exclusive alternatives, and wait for the user's direct reply.
In codex exec, background automation, CI, autopilot, or subagent execution,
never use the fallback and never fabricate intent. A caller that explicitly
requested a draft may receive only a best-effort PRD from supplied material,
with every unvalidated decision in Open Questions and a clear "interactive pass
required" status. Do not claim it is roadmap-ready and do not create or update
its roadmap or roadmap-MOC.
Workflow
Read and follow the shared PRD authoring protocol
before authoring. Determine whether the user is creating from an idea or updating
an existing PRD; before overwriting, confirm the exact output path and preserve
stable feature and SPEC identifiers for unchanged work. Use the shared
PRD template,
technical-roadmap template,
slicing heuristics, and, for
a new roadmap, roadmap-MOC template.
If docs/ai/specs/ubiquitous-language.md exists, read it first and use its
terms verbatim in the PRD. Apply the protocol's interview, update,
slicing/estimation, MOC, index, and verification rules. Report created or updated paths and recommend
$speckit-scaffold-spec <SPEC-ID> for the first ready entry.
What ships with it
1 file 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.
- today Changed · -217 lines · -95 tokens per session c7de90865c3f
- 6d ago First seen · 287 lines · 259 tokens per session scan A 5756bbbea158
speckit-prd is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 164 tokens to every session and 1,051 once invoked, about $0.0008 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-04.
Other skills, from other repositories
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
plan
Turns an approved design or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.
to-issues
Break a plan or PRD into vertical-slice issues on the project issue tracker.
to-prd
Synthesize the current conversation into a PRD and publish to the issue tracker. No interview — use what you already know.
spec-to-done
Drive a reviewed spec to evidence-backed, integrated closure — grill the spec at intake until it is fully understood, decompose it into owned work items, build each against targeted criteria, gate every merge per item, maintain a criterion-to-evidence ledger, and close only when an integrated done gate passes. Use…
triage
Move issues and external PRs through triage roles — categorise, verify, grill if needed, write agent-ready briefs.