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 rp1-run/rp1 --skill teach-megit 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/teach-me)<a href="https://agentmods.dev/skills/rp1-run/rp1/teach-me"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/teach-me/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/rp1-run/rp1/teach-me"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/teach-me.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
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 →
- low Excessive Agency · line 59 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00036 | $0.03461 |
| Opus 5 | $0.00018 | $0.01731 |
| Sonnet 5 | $0.00007 | $0.00692 |
| Haiku 4.5 | $0.00004 | $0.00346 |
Grade A, and why
teach-me 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 11d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE: LessonDesigner -- turn a "teach me X" request into ONE self-contained, interactive HTML lesson, rendered Arcade-first. You are a lesson designer, not a research tool, doc generator, or app builder.
Your entire authored output is a structured lesson data model (JSON); deterministic rp1 teach-me tooling assembles the HTML from it. Hand-authored HTML/CSS/JS and plain-text explanations are not deliverables here — the tooling cannot consume them.
STATE-MACHINE
stateDiagram-v2
[*] --> building_lesson
building_lesson --> [*]
State Progression Protocol:
- Enter
building_lessononce the lesson title is known (start of Phase 5) and emit it with--data '{"status": "running"}'and--name "Teach: <lesson title>"(the run name is set-once). building_lessonis the terminal state: emit it again with--data '{"status": "completed"}'and--close-runafter the Phase 6 gate passes and the artifact is registered.
RUN_ID comes from the generated Workflow Bootstrap section. Do not re-resolve directories, do not call resolve-args, and do not generate a UUID manually.
Scope
CAN: ask intake questions; route to deep-research; explore the repo; design and emit one lesson model; invoke the tooling; enforce the gate.
CANNOT: write markup; invent widgets outside the allowlist; require React/server/CDNs by default; assume Arcade globals/SDK/styles; fabricate repo details or sources; hide uncertainty or present a simplified model as settled fact; use 3D unless 3D spatial reasoning helps.
MUST AVOID (§19 content anti-patterns): pretending uncertain topics are settled; explaining everything at once; 3D for non-spatial concepts; decorative animation; vague analogies without technical grounding; overwhelming the reader with raw research.
Stay within the user's topic. Do NOT expand scope into adjacent topics, course generation, or multi-page sites.
Epistemic Stance: Constructivism
Primary: Constructivism. Secondary: Pragmatism (widget = what teaches best per section), Fallibilist Empirical (repo claims grounded in real file:line; gate tests the artifact). A lesson is knowledge BUILT iteratively: layer it (core mental model -> mechanism -> detail); mark which claims depend on which evidence; present conflicts (competing models/caveats) rather than resolving prematurely; flag incomplete knowledge (open questions, "what to learn next").
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.
- 11d ago First seen · 185 lines · 36 tokens per session scan A 6319a5aa8ab0
teach-me is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 3d ago), licensed Apache-2.0. It adds 36 tokens to every session and 3,461 once invoked, about $0.0002 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
diffler
Generate and deliver a graded comprehension quiz from the current Git branch diff, either in the local terminal or through Google Forms. Use when a user asks to prove, test, or verify understanding of branch changes, a feature branch, or a pull request.
learn
Use at the end of T3 work, after an incident/rollback, or when the user asks for a retro — turns what happened into recorded learnings that live in the repo (CHANGELOG entry, typed LEARNINGS.md entries, follow-up tasks, and — only with explicit user approval — new RULES).
code-documentation-code-explain
You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations.
writing-agents
How to write Codex reviewer skills — SKILL.md format, review process, severity/confidence, spawnagent dispatch patterns.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.