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 synthesizegit 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/synthesize)<a href="https://agentmods.dev/skills/juicesharp/rpiv-mono/synthesize"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/synthesize/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/synthesize"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/synthesize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 171 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]
- medium Excessive Agency · line 105 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.00162 | $0.04135 |
| Opus 5.5 | $0.00065 | $0.01654 |
| Sonnet 5.5 | $0.00032 | $0.00827 |
| Haiku 4.5 | $0.00016 | $0.00413 |
Grade A, and why
synthesize 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 6d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesize
You merge several independent per-slice designs into one coherent phased plan. One pass. You do not redesign a slice or write code — you reconcile and sequence what the slice designs already decided. This is the fan-in barrier: each design was produced blind to the others, so your job is to make them fit together. No subagents, no self-review — the workflow's grade panel judges the merged plan.
Input
$ARGUMENTS — flags (the orchestrator wires them from the fan-in):
--designs <path>(repeats) — per-slice design docs from the design fanout.--subplans <path>(repeats) — partial sub-plans from a cluster fanout (root mode).--research <path>(optional) — the research the slices rest on, for cross-slice constraints.--as-subplan(flag) — emit a sub-plan (partial mode) instead of a full plan.--cluster <k>(optional, partial mode) — the ordinal written into the sub-plan's_cluster-<k>.mdfilename. The cluster fanout supplies it; for manual partial invocation pick an unused<k>(scan.rpiv/artifacts/subplans/for existing*_cluster-<k>.mdand take the next unused positive integer) so a re-dispatched pass writes a distinct file and never clobbers a sibling sub-plan.--goal <path>(optional, root/flat) — the verbatim brief. Every ask it names is implemented by a phase or deferred under## Out of Scopewith a reason. Partial mode ignores it.--acceptance <path>(optional, root/flat) — the frozen acceptance inventory (items:, idsa1…). Every id is disposed in the frontmatteracceptance:block (step 3b). Partial mode ignores it; missing or unreadable → omit the block.
If neither --designs nor --subplans is present, print an error and stop.
Modes
Pick the mode from the flags — the work is the same fan-in reconciliation at three scales:
| Mode | Selected by | Reads | Writes to | Output kind |
|---|---|---|---|---|
| Flat (default) | --designs only |
every design | .rpiv/artifacts/plans/ |
full plan |
| Partial (per-cluster) | --designs … --as-subplan |
one cluster's designs | .rpiv/artifacts/subplans/ |
sub-plan |
| Root (merge) | --subplans … |
the cluster sub-plans | .rpiv/artifacts/plans/ |
full plan |
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.
- 6d ago Changed 03aa234c5c7d
- 1mo ago Changed · +19 lines 242d74b2d088
- 1mo ago Changed 0ffdfada5ecc
- 2mo ago First seen · 176 lines · 162 tokens per session scan A 8c89c63d8636
synthesize is a skill published in the GitHub repository juicesharp/rpiv-mono (934 stars, last pushed 6d ago), licensed MIT. It adds 162 tokens to every session and 4,135 once invoked, about $0.0006 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…