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/aibier/claude-em-toolkit/pr-descriptionnpx skills add Aibier/claude-em-toolkit --skill pr-descriptiongit clone --depth 1 https://github.com/Aibier/claude-em-toolkitWrote 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/aibier/claude-em-toolkit/pr-description)<a href="https://agentmods.dev/skills/aibier/claude-em-toolkit/pr-description"><img src="https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/pr-description.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.00034 | $0.00358 |
| Opus 5 | $0.00017 | $0.00179 |
| Sonnet 5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
pr-description 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
PR Description Drafter
Drafts a PR title and description from the diff against the base branch.
Steps
-
Determine the base branch (usually
mainormaster):git merge-base --fork-point main HEAD || git merge-base main HEAD -
Gather the change summary:
git log main..HEAD --oneline git diff main...HEAD --statRead the full diff (
git diff main...HEAD) only for files whose purpose isn't clear from the stat — don't paste the whole diff into the description. -
Draft using this template:
## Summary - <bullet: what changed and why, not a file-by-file list> - <bullet: 1-3 max> ## Test plan - [ ] <how to verify this change — be specific: commands, manual steps> -
Title: short imperative, under 70 chars, e.g.
Add retry logic to upload client. -
Show the draft to the user — don't open the PR yourself unless explicitly asked. If asked to open it, use
gh pr create --title ... --body "$(cat <<'EOF' ... EOF)".
Notes
- Focus the summary on why, not a restatement of the diff (good identifiers already say what).
- If the branch mixes unrelated changes, flag that to the user — it may be worth splitting into separate PRs.
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 · 45 lines · 34 tokens per session scan A 4721474d4b5d
pr-description is a skill published in the GitHub repository Aibier/claude-em-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 358 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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…