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/nimblepros/agent-skills/prnpx skills add NimblePros/agent-skills --skill prgit clone --depth 1 https://github.com/NimblePros/agent-skillsWrote 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/nimblepros/agent-skills/pr)<a href="https://agentmods.dev/skills/nimblepros/agent-skills/pr"><img src="https://agentmods.dev/badge/skills/nimblepros/agent-skills/pr.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.1 | $0.00042 | $0.00386 |
| Opus 5 | $0.00021 | $0.00193 |
| Sonnet 5 | $0.00008 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
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 5d 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
Create PR
Full lifecycle for taking changes from a branch through to a deployed, verified PR.
Phase 1: Gather Context
Use the AskUserQuestion tool to confirm:
Target branch (default: main)
If the branch name contains a work item ID, extract it automatically. If $ARGUMENTS contains a work item ID, prefer that.
git branch --show-current
git log main..HEAD --oneline
git diff -w main...HEAD --stat
Read the diff to understand what changed. Check for work item IDs in commit messages.
Phase 2: Validate
Merge latest main before creating the PR:
git fetch origin main
git merge origin/main
Phase 3: Create the PR
See references/pr-template.md for the full PR body template.
gh pr create \
--title "type(scope): subject" \
--body "$(cat <<'EOF'
<pr-body-from-template>
EOF
)"
The PR title must follow conventional commit format with a hard limit of 65 characters.
Phase 4: Verify Deployment
After creation, use the gh CLI to confirm the PR exists:
gh pr view --web
Rules
- Keep the description factual
- Never force-push or push to main/master without explicit confirmation
- Be succinct; prefer bullet points to long paragraphs
- Always link to work items when possible
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.
- 5d ago First seen · 68 lines · 42 tokens per session scan A 70bb4c1bedf5
pr is a skill published in the GitHub repository NimblePros/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 386 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…