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 notegit 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/note)<a href="https://agentmods.dev/skills/rp1-run/rp1/note"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/note/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/note"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/note.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.00030 | $0.01225 |
| Opus 5.5 | $0.00012 | $0.00490 |
| Sonnet 5.5 | $0.00006 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
note 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note Capture
Distill session context into a succinct, frontmatter-rich markdown note. One note per invocation. Notes persist under .rp1/work/notes/ w/ auto-maintained index and append-only log.
Directories
Use the pre-resolved workRoot from the generated Resolve Arguments section. All note paths resolve against workRoot -- never relative to a worktree.
Set NOTES_DIR = {workRoot}/notes.
Load Template
Read the note template for format reference:
plugins/base/skills/artifact-templates/templates/note/note.md
Use this template as the canonical structure for the note file. Do not deviate from the frontmatter schema or section order.
Generate Note
Semantic Title
Derive a descriptive title from session context (or TOPIC if provided). The title MUST communicate the note's subject at a glance.
- Good: "API Rate Limiting Decision", "Memory Leak Root Cause in Worker Pool"
- Bad: "Session Notes 2026-06-10", "Various Decisions"
Slug
Slugify title: lowercase, hyphens for spaces, strip non-alphanumeric chars.
File path: {NOTES_DIR}/{yyyy-mm-dd}-{title-slug}.md
Frontmatter
Populate all required fields per template:
| Field | Source |
|---|---|
date |
Today (YYYY-MM-DD) |
title |
Generated semantic title |
tags |
Inferred from session context; 2-5 tags |
related |
Wikilink cross-references to relevant notes/artifacts (see below) |
source_context |
One-line summary of session context |
status |
active (always) |
Cross-References
Infer related entries from session context:
- Other notes on related topics ->
[[{note-filename-without-ext}]] - Feature artifacts -> relative path from notes dir (eg
../features/rp1-note/requirements.md) - PRs, research reports, or other work artifacts -> wikilink or relative path
Include only contextually evident references. Do not fabricate connections.
Body Sections
Four fixed sections. Omit any section w/ no content for this session.
| Section | Content |
|---|---|
| Context | Why this note exists. 1-3 sentences. |
| Decisions | Bullet list: each item states decision + rationale. |
| Findings | Bullet list: key discoveries/facts. Factual, no hedging. |
| References | Wikilinks and URLs only; no prose. |
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 First seen · 178 lines · 30 tokens per session scan A f1155e43704f
note is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 20d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,225 once invoked, about $0.0001 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
atelier-orchestrator
Skill routing and workflow orchestration. Selects Inline Plan or Spec-backed Plan, routes to the correct workflow skill, and manages transitions between phases. Use when starting any conversation or task to determine which planning mode and skill apply.
atelier-setup
Configure a repository for Atelier's development workflow. Use only when explicitly invoked; inspect existing guidance, issue-tracker and domain-document conventions, preview the proposed configuration, and write only after approval. It does not install Atelier or initialize external tooling.
obsidian-organizer
File new notes into the right folder and audit/reorganize folder structure in the user's Obsidian vault, using the obsidian CLI and a single source-of-truth map note (00Index/FolderMap.md) that lives inside the vault. Use this whenever a note needs to be placed, filed, sorted, or moved into the vault; whenever the…
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
orca-cli
Use the public orca CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree"…