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 TechDufus/oh-my-claude --skill ralph-plangit clone --depth 1 https://github.com/TechDufus/oh-my-claudeWrote 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/techdufus/oh-my-claude/ralph-plan)<a href="https://agentmods.dev/skills/techdufus/oh-my-claude/ralph-plan"><img src="https://agentmods.dev/badge/skills/techdufus/oh-my-claude/ralph-plan/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/techdufus/oh-my-claude/ralph-plan"><img src="https://agentmods.dev/badge/skills/techdufus/oh-my-claude/ralph-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 377 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00052 | $0.02354 |
| Opus 5 | $0.00026 | $0.01177 |
| Sonnet 5 | $0.00010 | $0.00471 |
| Haiku 4.5 | $0.00005 | $0.00235 |
Grade A, and why
ralph-plan 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph Plan Skill
Structured PRD generation. Interview, research, plan, approve.
What is Ralph Plan?
Ralph Plan creates comprehensive Product Requirements Documents through a deliberate process:
- Interview Phase - Understand requirements through focused questions
- Research Phase - Analyze codebase via Explore/librarian
- Planning Phase - Generate structured plan with clear steps
- Approval Gate - User reviews, modifies, and approves the final PRD
The result is a battle-tested plan ready for implementation by any method the user chooses.
When This Skill Activates
| Category | Trigger Phrases |
|---|---|
| Start planning | /ralph-plan <topic>, create prd, generate prd, plan this |
| Check status | ralph-plan status |
| Resume | resume ralph-plan |
Workflow
Phase 1: Planning
Create a structured plan through interview and research.
Step 1: Initialize Draft
Create draft at .claude/plans/drafts/{topic-slug}.md with template:
# Planning Draft: {topic}
## Status
Phase: Interview
Started: {timestamp}
## Requirements
- [to be captured from interview]
## Decisions
- [choices made during interview]
## Research Findings
- [results from Explore/librarian]
## Open Questions
- [unanswered items]
Step 2: Interview
Conduct focused interview (3-5 questions based on complexity):
Core Questions:
- "What problem does this solve?" (understand context)
- "What's the scope - minimal viable vs complete?" (set boundaries)
- "Any constraints, non-goals, or things to avoid?" (define exclusions)
Follow-up Questions (as needed):
- Technical approach preferences
- Dependencies on other work
- Success criteria
Update draft after each answer.
Step 3: Research
Research the codebase before finalizing:
Agent: Explore
Task: Find relevant files for {topic}
Expected: List of files that will be affected
Agent: oh-my-claude:librarian
Task: Read and summarize key files
Expected: Summary of current implementation patterns
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 · 411 lines · 52 tokens per session scan A f44bb01c5e32
ralph-plan is a skill published in the GitHub repository TechDufus/oh-my-claude (176 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,354 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
taiyi-plan
A TaiyiForge planning step that turns a README, product requirements document, or technical plan into a list of separate project changes. Each change includes a suggested work profile, dependencies, and priority.
taiyi-design
A technical-design guide for planning software changes before implementation. It produces a DESIGN.md document comparing at least two approaches and recording the chosen structure and trade-offs.
taiyi-dev
A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
taiyi-review
A pre-merge review guide for checking code changes, design decisions, tests, and documentation. A merge adds reviewed changes to the main code branch.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.