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 commands/samqin123/claude_skill_pool/prdgit clone --depth 1 https://github.com/samqin123/Claude_skill_poolWrote 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/commands/samqin123/claude_skill_pool/prd)<a href="https://agentmods.dev/commands/samqin123/claude_skill_pool/prd"><img src="https://agentmods.dev/badge/commands/samqin123/claude_skill_pool/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.00013 | $0.00775 |
| Opus 5 | $0.00006 | $0.00387 |
| Sonnet 5 | $0.00003 | $0.00155 |
| Haiku 4.5 | $0.00001 | $0.00077 |
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 3d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generator
You are creating a detailed Product Requirements Document (PRD) that is clear, actionable, and suitable for implementation with the Ralph autonomous agent system.
Step 1: Ask Clarifying Questions
Ask the user 3-5 clarifying questions to understand the feature requirements. Each question should have lettered options (a, b, c, etc.).
Example format:
**Question 1**: What type of authentication do you need?
a) Email/password with session
b) OAuth (Google, GitHub)
c) Magic link authentication
d) Other (please specify)
Step 2: Generate PRD
Once you have enough information, generate a PRD in markdown format with the following structure:
# [Feature Name]
## Overview
[Brief description of what this feature does and why it matters]
## User Stories
### US-001: [Story Title]
**As a** [user type],
**I want** [feature],
**So that** [benefit].
**Acceptance Criteria:**
- [ ] [Specific, verifiable criterion 1]
- [ ] [Specific, verifiable criterion 2]
- [ ] Typecheck passes
### US-002: [Story Title]
[...]
Critical Rules for Ralph Compatibility
Story Sizing (MOST IMPORTANT)
Each user story MUST be completable in ONE iteration (one context window).
Right-sized stories:
- Add a database column and migration
- Add a UI component to an existing page
- Update a server action with new logic
- Add a filter dropdown to a list
Too big (split these):
- "Build the entire dashboard" → Split into: schema, queries, UI components, filters
- "Add authentication" → Split into: schema, middleware, login UI, session handling
Rule of thumb: If you cannot describe the change in 2-3 sentences, it is too big.
Story Ordering
Stories execute in priority order. Earlier stories must NOT depend on later ones.
Correct order:
- Schema/database changes (migrations)
- Server actions / backend logic
- UI components that use the backend
- Dashboard/summary views that aggregate data
Acceptance Criteria
All criteria must be verifiable (not vague).
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.
- 3d ago First seen · 139 lines · 13 tokens per session scan A 517e0da06624
prd is a command published in the GitHub repository samqin123/Claude_skill_pool (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 775 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.