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/marchatton/agent-skills/create-json-prdnpx skills add marchatton/agent-skills --skill create-json-prdgit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/marchatton/agent-skills/create-json-prd)<a href="https://agentmods.dev/skills/marchatton/agent-skills/create-json-prd"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/create-json-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.1 | $0.00051 | $0.01808 |
| Opus 5 | $0.00026 | $0.00904 |
| Sonnet 5 | $0.00010 | $0.00362 |
| Haiku 4.5 | $0.00005 | $0.00181 |
Grade A, and why
create-json-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 6d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generator (JSON Only)
Create a structured JSON PRD that Ralph can execute deterministically. This PRD is the single source of truth for stories, gates, and status.
This skill ingests PRD markdown written via $create-prd (for example prd.md / prd-overall.md / prds/<slice_id>_<slug>/prd.md) and produces the matching PRD JSON.
Important: Do NOT implement anything. Only generate JSON.
Inputs
Required:
- A PRD markdown file path (one of):
prd.md(single-PRD dossier)prd-overall.md(multi-PRD dossier overall/spine)prds/<slice_id>_<slug>/prd.md(multi-PRD dossier slice)- (Optional legacy naming)
prd-<slug>.mdif a dossier uses that pattern
Optional (for "no information loss"):
- Shaping inputs in the same dossier (if present):
brief.md,breadboard-pack.md,spike-investigation.md,risk-register.md
If the user only provides a feature description (no PRD markdown), NO-GO: ask them to create prd.md via $create-prd first.
Outputs
- Save the PRD JSON alongside the PRD markdown with the matching basename (per
docs/04-projects/AGENTS.md):prd.md->prd.jsonprd-overall.md->prd-overall.jsonprd-<slug>.md->prd-<slug>.jsonprds/<slice_id>_<slug>/prd.md->prds/<slice_id>_<slug>/prd.json
If the prompt provides an explicit output path, save to that path instead.
The Job
- Read the PRD markdown and extract all details needed for a deterministic PRD JSON.
- If required information is missing, invoke
$ask-questions-if-underspecifiedand ask clarifying questions (see below). - Always ask about quality gates (commands that must pass).
- Generate a detailed PRD JSON that follows the structure below and save it to the output path.
Step 1: Clarifying Questions (When Needed)
Only ask questions when the PRD markdown is missing required inputs for the JSON shape. If you need to ask questions, use $ask-questions-if-underspecified and follow its workflow.
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.
- 6d ago First seen · 181 lines · 51 tokens per session scan A e7600254ba2f
create-json-prd is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,808 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…