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 agentmods add skills/rp1-run/rp1/guidenpx skills add rp1-run/rp1 --skill guidegit 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/skills/rp1-run/rp1/guide)<a href="https://agentmods.dev/skills/rp1-run/rp1/guide"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/guide.svg" alt="Measured on agentmods" height="20"></a>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.00016 | $0.01571 |
| Opus 5 | $0.00008 | $0.00785 |
| Sonnet 5 | $0.00003 | $0.00314 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
guide 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/guide - rp1 Capability Guide
You help users discover, understand, and invoke rp1 skills. You answer questions about what rp1 can do, recommend the right skill for a task, explain workflow sequences, and offer to run skills on the user's behalf.
Companion Docs
Two reference files sit alongside this skill. Load them based on intent (see routing below):
- CATALOG.md -- Full skill catalog organized by category. Use for discovery, comparison, and "what can rp1 do?" questions.
- WORKFLOWS.md -- Multi-skill composition patterns. Use for workflow, sequencing, and "how do I do X end-to-end?" questions.
1. No-Question Mode (Capability Overview)
If QUESTION is empty or omitted, provide a concise capability overview:
- Read
CATALOG.md(companion doc, same directory as this skill). - Run
rp1 list --jsonto get installed skills. - Present a summary organized by category showing only skills installed on
CURRENT_HOST:- Category name and when to use it
- Skill names with one-line descriptions
- Highlight workflow skills (marked in catalog)
- End with: "Ask me anything about these skills, or tell me what you're trying to do and I'll recommend the right one."
2. Intent Classification
When QUESTION is provided, classify it into exactly one category:
| Intent | Signal | Source |
|---|---|---|
| discovery | "What skills...", "list...", "show me...", "what can rp1 do" | CATALOG.md |
| comparison | "Difference between...", "X vs Y", "which should I use", "when to use X over Y" | CATALOG.md |
| workflow | "How do I do X end-to-end", "what order", "after X what's next", "workflow for..." | WORKFLOWS.md |
| how-to | "How do I use X", "how to run", "what flags", "parameters for..." | WORKFLOWS.md, then CATALOG.md |
| troubleshooting | "X isn't working", "error with", "why does X fail", "can't find skill" | docs/reference/ files |
| meta | "How does rp1 work internally", "architecture of", "how is X built" | docs/reference/ files |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 140 lines · 16 tokens per session scan A f55a733b4944
guide is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,571 once invoked, about $0.0001 per session on Opus 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
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
pr-description-skill
Use this skill to write the PR description (PR body) for any pull request opened against microsoft/apm. Produces one self-sufficient GitHub-Flavored Markdown artifact: TL;DR, Problem (WHY), Approach (WHAT), Implementation (HOW), 1-3 validated mermaid diagrams, explicit trade-offs, validation evidence, and a…
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…