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-mono --skill plangit clone --depth 1 https://github.com/juicesharp/rpiv-monoWrote 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-mono/plan)<a href="https://agentmods.dev/skills/juicesharp/rpiv-mono/plan"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/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-mono/plan"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/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 MCP Rug Pull · line 407 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00084 | $0.06504 |
| Opus 5 | $0.00042 | $0.03252 |
| Sonnet 5 | $0.00017 | $0.01301 |
| Haiku 4.5 | $0.00008 | $0.00650 |
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 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.
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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Input
$ARGUMENTS — path to a design artifact (.rpiv/artifacts/designs/*.md).
Metadata
node "${SKILL_DIR}/../_shared/now.mjs"
echo
node "${SKILL_DIR}/../_shared/git-context.mjs"
Copy values verbatim — do not reformat the timezone offset.
Flow
- Input → 2. Inherit phase boundaries from design's
## Slices(1:1) → 3. Write plan (code from Architecture, Success Criteria pass through from## Slices) → 4. Independent Plan Review (code-reviewer + coverage-reviewer in parallel) → 5. Triage merged findings → 6. Follow-ups
The final artifact is implement-ready.
Steps
Step 1: Read Design Artifact
When this command is invoked:
-
Determine input mode:
Design artifact provided (path to a
.mdfile in.rpiv/artifacts/designs/):- Read the design artifact FULLY using the Read tool WITHOUT limit/offset
- Extract: Architecture (the code changes),
## Slices(slice boundaries + per-slice Success Criteria — authored by/skill:designStep 6.1, verified by slice-verifier at 6.2), File Map, Ordering Constraints, Verification Notes, Performance Considerations, Scope - These are the inputs for phasing.
## Slicesis the phase contract: each### Slice N: {name}becomes## Phase N: {name}with the same**Files**:list and the same Success Criteria. No reauthoring. - Design decisions are settled — do not re-evaluate them
- If the design has unresolved questions OR the
## Slicessection is missing/empty, 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 .rpiv/artifacts/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.
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 · 451 lines · 84 tokens per session scan A 5e07fe301b02
plan is a skill published in the GitHub repository juicesharp/rpiv-mono (773 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 6,504 once invoked, about $0.0004 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…