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 shubham0704/claude-skills --skill rpi-workflowgit clone --depth 1 https://github.com/shubham0704/claude-skillsWrote 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/shubham0704/claude-skills/rpi-workflow)<a href="https://agentmods.dev/skills/shubham0704/claude-skills/rpi-workflow"><img src="https://agentmods.dev/badge/skills/shubham0704/claude-skills/rpi-workflow/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/shubham0704/claude-skills/rpi-workflow"><img src="https://agentmods.dev/badge/skills/shubham0704/claude-skills/rpi-workflow.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.00062 | $0.00909 |
| Opus 5 | $0.00031 | $0.00454 |
| Sonnet 5 | $0.00012 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
rpi-workflow 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RPI Workflow: Research -> Plan -> Implement
A structured workflow for complex engineering tasks with Codex architectural review.
When to Invoke
- User says
/rpior "start RPI" - User wants structured research before implementation
- User wants Codex to review a plan
- User needs to create research docs or implementation plans
File Structure
All artifacts go in docs/ at the project root:
docs/
├── research/
│ └── YYYY-MM-DD-topic.md # Research findings
└── plans/
├── PLAN-<repo>-<task>.md # Claude creates
├── FEEDBACK-<repo>-<task>.md # Codex creates
├── IMPL-<repo>-<task>.md # Claude creates after implementation
└── VALIDATION-<repo>-<task>.md # Codex creates (optional)
Workflow Steps
Step 1: Research Phase
Launch parallel Explore agents to gather codebase understanding:
Task(subagent_type="Explore", prompt="Research how X works...")
Task(subagent_type="Explore", prompt="Research how Y connects to Z...")
Save findings to docs/research/YYYY-MM-DD-topic.md using the research template. For the template structure, see TEMPLATES.md.
Step 2: Plan Phase
Create docs/plans/PLAN-<repo>-<task>.md with:
- Goal (1-2 sentences)
- Key Files (
path:linereferences) - Problem (what's broken/missing)
- Proposed Solution (phased, with file-level changes)
- Success Criteria (checkboxes)
- Risks (numbered)
- Questions for Review (for Codex)
Step 3: Codex Review
Run from the project root:
codex exec --skip-git-repo-check "Read docs/plans/PLAN-<repo>-<task>.md and provide architectural feedback. Review the proposed solution, identify risks, suggest improvements. Write your feedback to docs/plans/FEEDBACK-<repo>-<task>.md"
Notes:
- Always use
--skip-git-repo-checkfor non-git repos - No
--quietflag exists - Codex writes feedback autonomously to the FEEDBACK file
Step 4: Read & Incorporate Feedback
Read docs/plans/FEEDBACK-<repo>-<task>.md and present key findings to the user:
- Executive assessment
- Missing edge cases
- Better abstractions suggested
- Risks not identified
- Phase reordering suggestions
- Actionable recommendations
What ships with it
2 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.
- 10d ago First seen · 102 lines · 62 tokens per session scan A 8a1107c00227
rpi-workflow is a skill published in the GitHub repository shubham0704/claude-skills (1 stars, last pushed 6d ago), licensed MIT. It adds 62 tokens to every session and 909 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-31.
Other skills, from other repositories
bug-report-writer
Converts rough notes, casual descriptions, console errors, or quick observations into professional, complete bug reports — exported as a formatted Excel (.xlsx) file ready for Excel, Google Sheets, Jira, or Azure DevOps. Use this skill whenever the user mentions: "write a bug report", "log a bug", "report this issue"…
daily-planner-prioritizer
Creates a smart, time-blocked daily plan from a user's task dump, meetings, errands, habits, and goals — then outputs BOTH a clean text summary in chat AND a formatted Excel (.xlsx) schedule file. Covers work tasks, meetings, personal errands, health/exercise reminders, and QA-specific tasks (test runs, bug triage…
recipe-grocery-list
Converts one or more recipes, a weekly meal plan, or even just dish names into a clean, categorized, deduplicated grocery shopping list — with quantities scaled to the number of servings needed. Also exports a formatted Excel (.xlsx) shopping list file. Use this skill whenever the user mentions: "make a grocery list"…
test-case-generator
Generates comprehensive, structured test cases from feature descriptions, user stories, requirements, or acceptance criteria — and exports them as a formatted Excel (.xlsx) file ready for use in Excel or Google Sheets. Use this skill whenever the user mentions: "write test cases", "generate test cases", "create test…
email-message-rewriter
Rewrites, polishes, or drafts emails and messages from rough notes, bullet points, or poorly worded drafts — in the right tone for the situation. Handles professional emails, Slack messages, WhatsApp texts, follow-ups, apologies, feedback, and more. Use this skill whenever the user says: "rewrite this email", "make…
a11y-security-generator
Generates Selenium Java wrappers for axe-core accessibility testing and OWASP UI/API security checks.