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/brenbuilds1/copilot-ralph/prdnpx skills add brenbuilds1/copilot-ralph --skill prdgit clone --depth 1 https://github.com/brenbuilds1/copilot-ralphWrote 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/brenbuilds1/copilot-ralph/prd)<a href="https://agentmods.dev/skills/brenbuilds1/copilot-ralph/prd"><img src="https://agentmods.dev/badge/skills/brenbuilds1/copilot-ralph/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.00069 | $0.02209 |
| Opus 5 | $0.00034 | $0.01104 |
| Sonnet 5 | $0.00014 | $0.00442 |
| Haiku 4.5 | $0.00007 | $0.00221 |
Grade A, and why
prd-generator 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 5d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generator
Create detailed Product Requirements Documents that are clear, actionable, and suitable for autonomous implementation by Ralph.
The Job
- Receive a feature description from the user
- Ask 3-5 essential clarifying questions (with lettered options)
- Generate a structured PRD based on answers
- Save to
prd.jsonin project root
Important: Do NOT start implementing. Just create the PRD.
Step 1: Clarifying Questions
Ask only critical questions where the initial prompt is ambiguous. Focus on:
- Problem/Goal: What problem does this solve? Why build this?
- Core Functionality: What are the key user actions?
- Scope/Boundaries: What should it NOT do?
- Technology: What stack/framework to use?
- Success Criteria: How do we know it's done?
Format Questions Like This:
1. What is the primary goal of this feature?
A. Improve user onboarding experience
B. Increase user retention
C. Reduce support burden
D. Other: [please specify]
2. Who is the target user?
A. New users only
B. Existing users only
C. All users
D. Admin users only
3. What is the scope?
A. Minimal viable version (MVP)
B. Full-featured implementation
C. Just the backend/API
D. Just the UI/frontend
4. What technology stack?
A. React + Node.js
B. Next.js
C. Plain HTML/CSS/JS
D. Other: [please specify]
5. What's explicitly OUT of scope?
A. Authentication/login
B. Database persistence
C. Mobile responsiveness
D. None of the above - include everything
This lets users respond with "1A, 2C, 3A, 4B, 5A" for quick iteration.
Step 2: Break Down Into User Stories
After gathering answers, break the feature into small, focused user stories.
Story Size Rule
Each story must be small enough to complete in one Ralph iteration (one agent context window, ~15-30 minutes of focused work).
Good story sizes:
- Add a single component
- Create one API endpoint
- Add form validation
- Create a database migration
- Wire up frontend to API
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.
- 5d ago First seen · 310 lines · 69 tokens per session scan A 7305fe677f65
prd-generator is a skill published in the GitHub repository brenbuilds1/copilot-ralph (50 stars, last pushed 7mo ago), licensed MIT. It adds 69 tokens to every session and 2,209 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-30.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…