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 RobinOppenstam/claude-ralph --skill prdgit clone --depth 1 https://github.com/RobinOppenstam/claude-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/robinoppenstam/claude-ralph/prd)<a href="https://agentmods.dev/skills/robinoppenstam/claude-ralph/prd"><img src="https://agentmods.dev/badge/skills/robinoppenstam/claude-ralph/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/robinoppenstam/claude-ralph/prd"><img src="https://agentmods.dev/badge/skills/robinoppenstam/claude-ralph/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.00000 | $0.00623 |
| Opus 5 | $0.00000 | $0.00311 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
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 9d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generation Skill
This skill helps you create detailed Product Requirements Documents (PRDs) for features you want to build.
Usage
Load this skill and say: "Create a PRD for [your feature description]"
Process
When asked to create a PRD, follow these steps:
1. Ask Clarifying Questions
Before writing the PRD, ask the user about:
- Target users: Who will use this feature?
- Core problem: What problem does this solve?
- Success metrics: How will we know it's successful?
- Technical constraints: Any specific tech stack, patterns, or limitations?
- Scope boundaries: What's explicitly NOT included?
- Dependencies: Does this depend on other features/systems?
2. Generate the PRD
Create a markdown document with these sections:
# PRD: [Feature Name]
## Overview
Brief description of the feature and its purpose.
## Problem Statement
What problem are we solving? Why now?
## Target Users
Who benefits from this feature?
## Goals & Success Metrics
- Goal 1: [metric]
- Goal 2: [metric]
## User Stories
### US-001: [Story Title]
**As a** [user type]
**I want to** [action]
**So that** [benefit]
**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
**Priority:** High/Medium/Low
**Estimate:** S/M/L
[Repeat for each story]
## Technical Considerations
- Architecture notes
- Database changes
- API endpoints
- Security considerations
## Out of Scope
- Explicit list of what's NOT included
## Dependencies
- External systems
- Other features
- Third-party services
## Risks & Mitigations
| Risk | Impact | Mitigation |
|------|--------|------------|
| Risk 1 | High | Mitigation strategy |
## Timeline
Rough estimates for each phase.
3. Save the PRD
Save the PRD to: tasks/prd-[feature-name-kebab-case].md
Tips for Good PRDs
- Right-sized stories: Each story should be completable in one coding session
- Clear acceptance criteria: Binary pass/fail, not subjective
- Include quality gates: typecheck, tests, lint must pass
- UI stories need browser verification: Always include "Verify in browser" criterion
- Order by dependency: Earlier stories shouldn't depend on later ones
- Include the "why": Context helps the implementer make good decisions
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.
- 9d ago First seen · 103 lines · 0 tokens per session scan A 6019d39afca2
prd is a skill published in the GitHub repository RobinOppenstam/claude-ralph (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 623 tokens. 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…