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 richardcb/oh-my-gemini --skill prd-creationgit clone --depth 1 https://github.com/richardcb/oh-my-geminiWrote 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/richardcb/oh-my-gemini/prd-creation)<a href="https://agentmods.dev/skills/richardcb/oh-my-gemini/prd-creation"><img src="https://agentmods.dev/badge/skills/richardcb/oh-my-gemini/prd-creation/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/richardcb/oh-my-gemini/prd-creation"><img src="https://agentmods.dev/badge/skills/richardcb/oh-my-gemini/prd-creation.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.00051 | $0.01146 |
| Opus 5 | $0.00026 | $0.00573 |
| Sonnet 5 | $0.00010 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
prd-creation 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 10d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Creation Skill
Goal
To guide an AI assistant in creating a single, comprehensive Product Requirements Document (PRD) in Markdown format. This document will serve as both a high-level brief for project context and a detailed, actionable guide for implementation.
Activation Triggers
- User asks to "create a PRD", "write requirements", or "define a feature"
- Starting a new feature that needs requirements definition
- User says "docs first" or "requirements first"
Bundled Resources
This skill includes:
scripts/generate-prd.sh- Shell script to create PRD file with proper namingtemplates/prd-template.md- Standard PRD template
Process
1. Receive Initial Prompt
The user provides a brief description or request for a new feature.
2. Detect Existing PRDs
Check if PRDs already exist:
ls -la features/*prd*.md 2>/dev/null || ls -la docs/prds/*.md 2>/dev/null || echo "NO_EXISTING_PRDS"
3. Ask Clarifying Questions
Before writing the PRD, you must ask clarifying questions to gather sufficient detail. Group related questions and provide numbered options for easy responses.
Problem & Goal
- "What is the core problem this feature solves for the user?"
- "What is the main goal we want to achieve?"
- "Why is this important now?"
Target User
- "Who is the primary user of this feature?"
- "Are there secondary users or stakeholders?"
Core Functionality
- "What are the key actions a user must be able to perform?"
- "What does success look like for this feature?"
User Stories
- "Could you provide a few user stories? (e.g., As a [user], I want to [action] so that [benefit].)"
Scope Boundaries
- "What's explicitly out of scope for this version?"
Edge Cases & Failures
- "What happens when things go wrong?"
- "Are there any business rules that must never be violated?"
4. Generate PRD
Use the template structure to create the PRD:
# Generate next PRD number
NEXT_NUM=$(ls features/*prd*.md 2>/dev/null | wc -l)
NEXT_NUM=$((NEXT_NUM + 1))
PADDED_NUM=$(printf "%04d" $NEXT_NUM)
What ships with it
2 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.
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.
- 10d ago First seen · 176 lines · 51 tokens per session scan A ee136bd63cb0
prd-creation is a skill published in the GitHub repository richardcb/oh-my-gemini (16 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,146 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
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-doc
Create and maintain an intuitive human documentation surface for AI-agent-developed repos. Use when humans should only need README.md, ARCHITECTURE.md, STATUS.md, and docs/human/ while planning logs, generated docs, retrospectives, ADR detail, and implementation evidence stay in AI-agent-only folders.
intuitive-refactor
Refactor and cleanup router for known code/module/API seams, stale surfaces, compatibility shims, architecture cleanup targets, changed-code quality review, oversized modules, repeated cleanup campaigns, and recurring whole-repo architecture maintenance goals. Use this when the user names a concrete seam, wants…
intuitive-shape
Shape a raw product or project idea into a bounded decision before planning or implementation. Use when deciding whether an idea deserves a bet, setting an appetite, comparing candidate bets under finite capacity, cutting scope, exposing rabbit holes and no-gos, or choosing BET, RESEARCH, RESHAPE, or PASS. This skill…
skill-runner
Run a bounded development task through named skills in an isolated, tmux-backed Codex or Claude session. Use for durable or artifact-sensitive worker phases, supervised skill runs, and post-run skill evaluation.