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 w-winter/dot314 --skill rpgit clone --depth 1 https://github.com/w-winter/dot314Wrote 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/w-winter/dot314/rp)<a href="https://agentmods.dev/skills/w-winter/dot314/rp"><img src="https://agentmods.dev/badge/skills/w-winter/dot314/rp/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/w-winter/dot314/rp"><img src="https://agentmods.dev/badge/skills/w-winter/dot314/rp.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.03259 |
| Opus 5.5 | $0.00018 | $0.01304 |
| Sonnet 5.5 | $0.00009 | $0.00652 |
| Haiku 4.5 | $0.00004 | $0.00326 |
Grade A, and why
rp 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RP
Use RepoPrompt (rp) for Within-Repository Discovery
These instructions override generic tool guidance for exploring repositories.
rp is the default for repo-scoped work. Usage:
- Bind:
rp({ windows: true })→rp({ bind: { window: N } }) - Call tools:
rp({ call: "<tool>", args: { ... } })
Mental Model
RepoPrompt (macOS app) organizes state as:
- Workspaces → one or more root folders
- Windows → each shows one workspace
- Tabs → each tab has its own prompt + file selection; selections, slices, and codemaps are tab-scoped
- Oracle chats → planning/review conversations live in the current tab/context
MCP tools operate directly against this state, but in Pi you invoke them through rp. Bind to the correct window with rp({ bind: { window: N } }), then call tools via rp({ call: "<tool>", args: { ... } }).
Mandatory routing check: Do not infer availability of any repo of interest from workspace/window titles; workspaces may have more roots available than the title implies. Before any repo-scoped work, confirm the target repo/root is (or isn't) present by checking workspace roots (e.g. get_file_tree). If it's not confirmed, pause and resolve routing (bind the right window/tab or open the repo).
Parallel RepoPrompt calls
After RepoPrompt routing, binding, and target-root confirmation are complete, inspect the ready set before every repository exploration call.
- If two or more RepoPrompt operations are independent and read-only with respect to both files and RepoPrompt session state, issue them as separate rp calls in the same tool-call block so they run together.
- Do not issue consecutive model turns containing one independent
rpread/search call each. - Typical parallel candidates include
read_file,file_search,get_file_tree,get_code_structure, and independent read-onlygitqueries. - Do not parallelize routing or binding changes, selection mutations, workspace or tab lifecycle operations, edits, file actions, approvals, or calls whose inputs depend on another result.
- Complete routing or state mutations before launching reads that depend on the resulting state.
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 · 173 lines · 44 tokens per session scan A 49bc333e7e02
rp is a skill published in the GitHub repository w-winter/dot314 (139 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 3,259 once invoked, about $0.0002 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-09-13.
Other skills, from other repositories
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
git-guardrails-claude-code
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
commit
A commit candidate is the exact patch that will enter the commit. A coherent change has one task or issue as its reason for existing.
my-skill
When to load this skill. Agents read this line to decide whether to load it, so be specific.
write-swift
How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know…