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/justinthomas2/agentrc/open-prnpx skills add JustinThomas2/agentrc --skill open-prgit clone --depth 1 https://github.com/JustinThomas2/agentrcWhat 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 | $0.00031 | $0.00574 |
| Opus 5 | $0.00015 | $0.00287 |
| Sonnet 5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
open-pr 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 2d 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
ISSUE = $ARGUMENTS — if that reads as a literal placeholder instead of a number, use the issue number I gave when invoking this skill. If I gave none, ask for it before doing anything else.
Your task
- Run
git status -sbandgit log main..HEAD --onelineto see what is being opened for review. If the working tree is dirty or there are no commits ahead of main, stop and tell me instead of pushing. - No pre-push sync is needed. If GitHub reports the opened PR cannot
be merged cleanly, then per AGENTS.md: pull main, rebase this branch
onto it, resolve conflicts, and push with
--force-with-lease, never bare--force. - Read the PR body template bundled with this skill at
pr-template.md. - Compose the PR title and body, filling every section of that template:
- title aligned with the primary commit
- the AI-attribution marker (per AGENTS.md) at the top of the body, exactly as it appears in the template - any hand-written sections I add during review go above it
- a summary of what changed and why
- the testing you performed
Closes #ISSUEin the body
- STOP — show me the complete title and body as plain text in the
conversation and wait for my approval; revise until I approve. Command
approval prompts only show the command (often just a
--body-filepath), so this chat text is my only chance to actually read what is about to be posted. - Push the current branch to origin with upstream tracking. (This will ask for my approval — that is intentional; wait for it.)
- Open the PR with
gh pr create, using the approved title and body exactly. (This will also ask for my approval — wait for it.) - Reply with the PR URL. Then STOP. Once review feedback arrives, I'll
invoke
address-feedbackwith PR N.
What ships with it
1 file 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.
- 2d ago First seen · 43 lines · 31 tokens per session scan A 48f9e615b4c2
open-pr is a skill published in the GitHub repository JustinThomas2/agentrc (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 574 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…