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 joaquimscosta/arkhe-claude-plugins --skill ralph-prdgit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/ralph-prd)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/ralph-prd"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/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/joaquimscosta/arkhe-claude-plugins/ralph-prd"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/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.00063 | $0.01068 |
| Opus 5.5 | $0.00025 | $0.00427 |
| Sonnet 5.5 | $0.00013 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
ralph-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 yesterday.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph PRD Creation
Interactive wizard to create Product Requirements Document and Ralph project setup with task sets.
Quick Start
/create-prd # Start interactive wizard
/create-prd "Build a todo app" # Start with description
What It Creates
project/
├── PROMPT.md # Instructions for each iteration
├── ralph.sh # Loop runner (executable)
└── .ralph/
├── current-taskset -> tasksets/initial # Symlink to active taskset
└── tasksets/
└── initial/ # Your task set (named during setup)
├── tasks.json # Task list (JSON)
├── prd.md # Requirements (Markdown)
├── memories.md # Persistent learnings
├── config.json # Ralph settings
└── activity.log # Iteration log (empty)
Discovery Questions
Ask these discovery questions:
- Task Set Name - What should this collection be called? (default: "initial")
- Problem - What problem are you solving?
- Audience - Who is the target user?
- Features - What are the 3-5 core features?
- Tech Stack - What technologies to use?
- Architecture - Monolith, microservices, etc.?
- UI/UX - Visual requirements and preferences?
- Auth - Authentication needs?
- Integrations - Third-party services?
- Success Criteria - How do we know it's done?
Question Specificity for Destructive Operations
When discovery questions involve deleting files, removing dependencies, or other destructive changes:
- Always include full paths of items being deleted or modified
- State size/scope — file count, line count, component count
- Explicitly state what will NOT be affected
- Frame as confirmation, not open question — "Deleting X, Y, Z. Proceed?" not "What should be deleted?"
See EXAMPLES.md for vague-vs-specific anti-patterns.
What ships with it
8 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.
- yesterday First seen · 111 lines · 63 tokens per session scan A 823357dd1a06
ralph-prd is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,068 once invoked, about $0.0003 per session on Opus 5.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-10-16.
Other skills, from other repositories
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…
pm
Universal, project-agnostic PRODUCT MANAGER playbook — the scope-disciplined PM that plans a project, gates its launch, and says no. Five modes, one workflow each: prd (turn a spec or a user request into a build-ready PRD — objectives, in-scope, out-of-scope guards, an acceptance-criteria table mapping every success…
docs-project-management
Universal, project-agnostic playbook for managing an ENTIRE project inside the repo's docs/ folder — the docs/-native system of record, reusable in any project, new or existing, with no external issue tracker. Defines WHAT it manages: the work-item TAXONOMY (Roadmap → docs/ROADMAP.md + docs/roadmap.json, PRD →…
execute
Execute phase — wave-based crew dispatch with critic gates and evidence-based verification.
recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.