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 juicesharp/rpiv-pi --skill plangit clone --depth 1 https://github.com/juicesharp/rpiv-piWrote 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/juicesharp/rpiv-pi/plan)<a href="https://agentmods.dev/skills/juicesharp/rpiv-pi/plan"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-pi/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/juicesharp/rpiv-pi/plan"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-pi/plan.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.00032 | $0.02460 |
| Opus 5 | $0.00016 | $0.01230 |
| Sonnet 5 | $0.00006 | $0.00492 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
plan scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] API endpoint returns 200: `curl localhost:8080/api/new-endpoint` How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Plan
You are tasked with creating phased implementation plans from design artifacts. The design artifact contains all architectural decisions, full implementation code, and ordering constraints. Your job is to decompose that design into parallelized atomic phases with success criteria that implement can execute.
Step 1: Read Design Artifact
When this command is invoked:
-
Determine input mode:
Design artifact provided (path to a
.mdfile inthoughts/shared/designs/):- Read the design artifact FULLY using the Read tool WITHOUT limit/offset
- Extract: Architecture (the code changes), File Map, Ordering Constraints, Verification Notes, Performance Considerations, Scope
- These are the inputs for phasing
- Design decisions are settled — do not re-evaluate them
- If the design has unresolved questions, STOP — tell the developer to return to design
No arguments provided:
I'll create an implementation plan from a design artifact. Please provide the path: `/skill:plan thoughts/shared/designs/2025-01-20_09-30-00_feature.md` Run `/skill:design` first to produce the design artifact. There is no standalone path.Then wait for input.
-
Read any additional files mentioned in the design's References — research documents, tickets. Read them FULLY for context.
Step 2: Decompose into Phases
Read the Ordering Constraints and File Map from the design artifact. Apply phasing rules:
- Independently implementable: Each phase must compile and pass tests on its own — no cross-phase runtime state
- Parallelizable: Phases that don't depend on each other are explicitly marked (e.g., "Phases 2 and 3 can run in parallel")
- Worktree-sized: Each phase should be appropriate for a single implement session in a worktree (~3-8 files changed, 1-3 components touched)
- Dependency-ordered: Phase ordering follows the design artifact's Ordering Constraints
- Grouped coherently: Related file changes go in the same phase (e.g., import change + hook setup + JSX modification for one component)
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.
- 9d ago First seen · 282 lines · 32 tokens per session scan A 1b0ec902ddfc
plan is a skill published in the GitHub repository juicesharp/rpiv-pi (11 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 2,460 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…