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/base)<a href="https://agentmods.dev/plugins/rp1-run/rp1/base"><img src="https://agentmods.dev/badge/plugins/rp1-run/rp1/base/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/base"><img src="https://agentmods.dev/badge/plugins/rp1-run/rp1/base.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rp1-base 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 20d 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-base",
"description": "Core knowledge management, documentation generation, and strategic analysis for Claude Code",
"version": "0.7.16",
"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": [
"knowledge-management",
"documentation",
"strategic-analysis",
"security-validation",
"content-writing"
]
}
What it installs
The manifest is a name and a version. 21 skills, 17 agents, 1 hook travel with it, and installing the plugin installs all of them — 987 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill deep-research A 25 tokens
- Skill markdown-preview A 30 tokens
- Skill mermaid A 36 tokens
- Skill teach-me A 36 tokens
- Skill artifact-templates A 27 tokens
- Skill generate-user-docs A 29 tokens
- Skill guide A 16 tokens
- Skill prompt-writer A 29 tokens
- Skill socratic-duel A 26 tokens
- Skill socratic-duel-run A 24 tokens
- Skill task A 10 tokens
- Skill write-content A 20 tokens
- Skill analyse-security A 35 tokens
- Skill code-comments A 27 tokens
- Skill note A 30 tokens
- Skill project-birds-eye-view A 44 tokens
- Skill self-update A 14 tokens
- Skill rp1-migrate A 18 tokens
- Skill fix-mermaid A 32 tokens
- Skill knowledge-build A 25 tokens
- Skill strategize A 29 tokens
- Agent project-documenter A 34 tokens
- Agent prompt-pipeline-runner A 30 tokens
- Agent socratic-duel-participant A 28 tokens
- Agent kb-architecture-mapper A 23 tokens
- Agent kb-feature-extractor A 22 tokens
- Agent kb-module-analyzer A 21 tokens
- Agent kb-spatial-analyzer A 29 tokens
- Agent research-reporter A 16 tokens
- Agent security-validator A 29 tokens
- Agent kb-concept-extractor A 21 tokens
- Agent kb-index-builder A 20 tokens
- Agent kb-pattern-extractor A 21 tokens
- Agent mermaid-fixer A 46 tokens
- Agent research-explorer A 19 tokens
- Agent scribe A 15 tokens
- Agent strategic-advisor A 30 tokens
- Agent kb-interaction-mapper A 21 tokens
- Hook SessionStart A not measured
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.
- 20d ago Changed 8ff3a18a5a68
- 23d ago Changed 4336d0100d1e
- 1mo ago Changed 8e47ccca913b
- 1mo ago First seen · 20 lines scan A 455519d380dd
rp1-base is a plugin published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 20d 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-08-30.
Other plugins, from other repositories
turing
Autonomous state machine for cognitive continuity. Preserves session state before context compaction and restores it on session start. Features priority-based selective restore, token budget tracking, auto decision extraction, and state archiving. Based on Alan Turing's 1936 paper 'On Computable Numbers'.
ultracontext
Cross-agent session portability. Powered by UltraContext.
titen-memory
Use Titen's evidence-grounded collaborative memory. The local stdio mode needs no configuration; a served Titen endpoint is the alternative for a shared store.
halomem
HaloMem organizational memory: session-start recall, session-end capture, MCP tools. Configure with HALOMEMURL and HALOMEMAPIKEY.
context-bank
Keep AI project memory small, in git, and shared across tools. Teaches Claude the retrieval-first .ai/ contract, checks bank health at session start, and adds doctor, compact and init commands.
ai-context-kit marketplace
Context-aware AI collaboration skills for creating and validating user context, project AGENTS.md files, and skill artifacts across LLM providers.