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.
git clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/plugins/rp1-run/rp1/utils)<a href="https://agentmods.dev/plugins/rp1-run/rp1/utils"><img src="https://agentmods.dev/badge/plugins/rp1-run/rp1/utils/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/plugins/rp1-run/rp1/utils"><img src="https://agentmods.dev/badge/plugins/rp1-run/rp1/utils.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rp1-utils 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 3d 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.
What it actually says
{
"name": "rp1-utils",
"description": "Meta tools for rp1 developers: prompt engineering, agent refactoring, and workflow optimization",
"version": "0.6.5",
"author": {
"name": "Prem Pillai (https://rp1.run)",
"email": "[email protected]"
},
"license": "Apache-2.0",
"homepage": "https://github.com/rp1-run/rp1",
"repository": "https://github.com/rp1-run/rp1",
"keywords": [
"prompt-engineering",
"agent-development",
"refactoring",
"meta-tools",
"rp1-development"
]
}
What it installs
The manifest is a name and a version. 4 skills, 1 agent travel with it, and installing the plugin installs all of them — 106 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 20 lines scan A 7deaf10eef6e
rp1-utils is a plugin published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 3d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-07.
Other plugins, from other repositories
persona-harness
Persona Harness shared skills and opt-in targeted Context for Claude Code.
rashomon
Evaluate prompts and skills through parallel execution comparison in git worktrees. Prompt optimization with BP-001009 patterns, skill creation/update with quality grading, and blind A/B evaluation.
interview-me
Deep-dive spec interviewer that produces production-grade specs through rigorous 1-on-1 interviews, with --verify drift detection against the codebase.
handoff
Portable project memory + development workflow for coding agents: auto-loads STATUS+RULES each session, enforces folder-level CONTEXT.md on edit, nudges durable state updates at turn end, scaffolds the system into any repo via guided discovery, and ships a tiered 6-phase workflow skill set covering every phase (brief.
repo-scaffold
Analyzes your repository and generates CLAUDE.md and project-specific skills.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.