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/jimmypaolini/codebase/update-pull-requestnpx skills add JimmyPaolini/codebase --skill update-pull-requestgit clone --depth 1 https://github.com/JimmyPaolini/codebaseWrote 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/jimmypaolini/codebase/update-pull-request)<a href="https://agentmods.dev/skills/jimmypaolini/codebase/update-pull-request"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/update-pull-request.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 | $0.00058 | $0.01557 |
| Opus 5 | $0.00029 | $0.00779 |
| Sonnet 5 | $0.00012 | $0.00311 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
update-pull-request 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 yesterday.
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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Pull Request
This skill teaches how to update an existing pull request's title and description so they accurately reflect the implemented changes.
When to Use This Skill
- A PR description is outdated or no longer matches the implementation
- You want to sync the PR title and description with the latest changes on the branch
- Addressing reviewer feedback about unclear PR descriptions
- After significant changes to the branch that alter the scope or intent
PR Conventions
All PR title rules, validation requirements, and description templates follow the same conventions as creating PRs. See create-pull-request skill for complete details.
Title Format
<type>(<scope>): <gitmoji> <subject>
- Format:
<type>(<scope>): <gitmoji> <subject>(max 128 chars) - Subject: Imperative mood, lowercase after gitmoji, no period
- Gitmoji: Must match the type (✨ feat, 🐛 fix, 📝 docs, ♻️ refactor, 🔧 chore, ⬆️ dependencies, etc.)
Description Template
## 🌰 Summary
<!-- Brief description of what this PR does (1-2 sentences) -->
## 📝 Details
- <!-- List of specific changes made -->
## 🧪 Testing
1. <!-- How to manually verify these changes work correctly -->
## 🔗 Related
- <!-- Link any relevant documentation or related resources like internal documentation, GitHub issues/pull requests -->
Workflow
Step 1 — Identify the Active Pull Request
Determine the current branch and locate its open PR:
git rev-parse --abbrev-ref HEAD
gh pr view --json number,title,body,baseRefName
If no PR exists, inform the user and suggest using the create-pull-request skill instead.
Step 2 — Gather the Full Diff
Get the complete set of changes between the base branch and HEAD:
git log origin/main..HEAD --oneline
git diff origin/main..HEAD --stat
git diff origin/main..HEAD
For large diffs, also review individual commits to understand intent:
git log origin/main..HEAD --format="%h %s"
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.
- yesterday First seen · 207 lines · 58 tokens per session scan A 8451ae601169
update-pull-request is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,557 once invoked, about $0.0003 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-09-03.
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…