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/ralphgit 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/ralph)<a href="https://agentmods.dev/commands/samqin123/claude_skill_pool/ralph"><img src="https://agentmods.dev/badge/commands/samqin123/claude_skill_pool/ralph.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.00012 | $0.01537 |
| Opus 5 | $0.00006 | $0.00768 |
| Sonnet 5 | $0.00002 | $0.00307 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
ralph 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 4d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph - Autonomous Agent Loop
Ralph implements PRDs by repeatedly spawning fresh AI instances to complete user stories one by one.
Phase 1: PRD Conversion (if markdown PRD provided)
Step 1: Check Input
Check if the user provided a path to a PRD file. If not, look for prd.json in the project root.
User input formats:
/ralph tasks/prd-my-feature.md- Convert PRD and run Ralph/ralph prd.json- Run Ralph with existing prd.json/ralph- Run Ralph (looks for prd.json)
Step 2: Archive Previous Run (if needed)
Check if prd.json exists with a different branchName. If so:
- Read current
prd.jsonand extractbranchName - Check if it differs from the new feature's branch
- If different AND
prd-progress.txthas content:- Create archive folder:
.claude/archive/YYYY-MM-DD-[feature-name]/ - Copy current
prd.jsonandprd-progress.txtto archive - Reset
prd-progress.txtwith fresh header
- Create archive folder:
Step 3: Convert to prd.json
Parse the PRD and generate prd.json in the project root:
{
"project": "[Project Name from PRD or auto-detected]",
"branchName": "ralph/[feature-name-kebab-case]",
"description": "[Feature description from PRD]",
"userStories": [
{
"id": "US-001",
"title": "[Story title]",
"description": "As a [user], I want [feature] so that [benefit]",
"acceptanceCriteria": [
"Criterion 1",
"Criterion 2",
"Typecheck passes"
],
"priority": 1,
"passes": false,
"notes": ""
}
]
}
Conversion Rules
- Each user story becomes one JSON entry
- IDs: Sequential (US-001, US-002, etc.)
- Priority: Based on dependency order (schema → backend → UI)
- All stories:
passes: falseand emptynotes - branchName: Derive from feature name, kebab-case, prefixed with
ralph/ - Always add: "Typecheck passes" to every story
- For UI stories: Add "Verify in browser using dev-browser skill"
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.
- 4d ago First seen · 227 lines · 12 tokens per session scan A 18ba28d4de8d
ralph is a command published in the GitHub repository samqin123/Claude_skill_pool (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,537 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.