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 amendgit 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/amend)<a href="https://agentmods.dev/skills/juicesharp/rpiv-mono/amend"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/amend/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/amend"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/amend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00101 | $0.01879 |
| Opus 5.5 | $0.00040 | $0.00752 |
| Sonnet 5.5 | $0.00020 | $0.00376 |
| Haiku 4.5 | $0.00010 | $0.00188 |
Grade A, and why
amend 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 1mo 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amend
You surgically fix one artifact so it clears the dimensions a grade panel marked failing. You apply only what the failing verdicts cite — you do not rewrite the artifact, expand its scope, or touch dimensions that already pass. One pass, non-interactive. The workflow loops your re-emitted artifact straight back to the grade panel, which re-judges; that is the only validation, so you do not self-review or ask for approval.
Input
$ARGUMENTS — flags the orchestrator wires from the gate's channels. Parse them generically, agnostic to the channel name:
- Verdicts — every flag whose name ends in
-verdicts(e.g.--research-verdicts,--plan-verdicts), repeatable. Each value is a verdict JSON path. - Citation floors — every flag whose name ends in
-cite-check(e.g.--plan-cite-check,--code-cite-check), repeatable. Each value is a cite-check verdict JSON path. - Lineage sources — the read-only context flags
--goal,--research,--acceptance, and--subplans(repeatable; build's fix arms only).--goalis the verbatim brief,--researchthe architecture/precedent findings,--acceptancethe frozen inventory,--subplansthe per-cluster sub-plans. They are context, never the artifact to re-emit. - Artifact — the single remaining
--<channel>flag that is not a verdicts, citation-floor, or lineage-source flag (i.e. not ending in-verdictsor-cite-check, and not--goal/--research/--subplans). Its value is the artifact to fix and re-emit; for both build fix arms this resolves to--plans.
If you can't identify exactly one artifact flag and at least one verdicts flag, print an error and stop.
Metadata
node "${SKILL_DIR}/../_shared/now.mjs"
The first tab-separated field is <iso> (use as last_updated).
Steps
- Read the artifact fully (no limit/offset) and read every verdict JSON.
- Select the failing findings. Group verdicts by
dimension; for each dimension keep the latest (bygraded_at) — verdicts accumulate across amend loops, so an older failing verdict may already be superseded. From the latest-per-dimension set, take those withpass: false, and also any carrying a non-emptyrisk_duty_demotionsarray (a field the workflow stamps after grading — even when the verdict's ownpassistrue, a demoted risk ruling records the demotion there). Additionally, from each PASSING dimension's latest verdict, select any finding that asserts a deterministic failure-as-written — the emitted code or edit fails typecheck/compile as written, a cited file or symbol does not exist, an edit anchor does not match its target. Left in place, such a finding is a landmine: a later round's grader will rate it blocking and it then costs a whole extra grade-fix lap. Select only that class from passing verdicts — every other finding on a passing verdict stays out of scope. If this selects nothing, the artifact already passes: re-emit it unchanged (only bumplast_updated) and report — the panel will confirm. - Apply each selected verdict's
feedback/findingssurgically (for a passing verdict, only its selected failure-as-written findings — itsfeedbackis not an instruction set). Use each finding'swhereto locate the exact spot and change only that. Honorfeedbackas the instruction set. Where a finding requires checking the codebase (acorrectnessorpattern-followingfix), Read/Grep the citedfile:lineto ground the edit — but never edit code, only the artifact. A completeness-class finding (the artifact under-covers the brief) is repaired from the lineage sources —--goal,--research,--subplans— by reading the authoritative source there and folding the missing point in; never reconstruct the missing content from verdict prose or guess it from a directory listing. - Confirm coverage — every selected finding maps to an edit you made. Do not introduce changes no finding asked for.
- Re-emit the artifact to the SAME path (Edit in place; Write only if a structural rewrite of a section is unavoidable). Preserve everything outside the cited findings, keep
status: ready, and updatelast_updated: <iso>in the frontmatter. Same path ⇒ the artifact's channel updates latest-wins for re-judging. - Print the artifact path, then a one-line summary:
amended for <dimensions>: <k> findings addressed.
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.
- 1mo ago Changed f1fb798df446
- 1mo ago Changed e91851d95369
- 2mo ago First seen · 53 lines · 101 tokens per session scan A 7742f43608f9
amend is a skill published in the GitHub repository juicesharp/rpiv-mono (934 stars, last pushed 6d ago), licensed MIT. It adds 101 tokens to every session and 1,879 once invoked, about $0.0004 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…