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 notorious-ai/claude-plugins --skill writing-pull-requestsgit clone --depth 1 https://github.com/notorious-ai/claude-pluginsWrote 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/notorious-ai/claude-plugins/writing-pull-requests)<a href="https://agentmods.dev/skills/notorious-ai/claude-plugins/writing-pull-requests"><img src="https://agentmods.dev/badge/skills/notorious-ai/claude-plugins/writing-pull-requests.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.00058 | $0.02793 |
| Opus 5 | $0.00029 | $0.01396 |
| Sonnet 5 | $0.00012 | $0.00559 |
| Haiku 4.5 | $0.00006 | $0.00279 |
Grade A, and why
Writing Pull Requests 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 7d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Pull Requests
Code diffs already show what changed, so retelling the diff in prose wastes the reader's time. The PR title and description convey motivation, impact, and context that accelerates review.
The problem space normally lives in a linked issue. When no issue exists, as for plenty of worthwhile changes, the description's opening paragraph stands in for one: a single paragraph carrying the friction and its cost is enough before the solution's story begins.
Core Principle: Repository Transformation
The PR title describes how the repository changes when the PR merges. The verb targets the repository capability, not the developer action.
The "Fill in the Blank" Technique
Complete this sentence with your title: "After this PR merges, the repository will _____."
The verb must make grammatical sense in this frame. Developer-action verbs fail the test:
| Verb | "The repository will _____" | Works? |
|---|---|---|
| Parse MAC addresses | "The repository will parse MAC addresses" | Yes |
| Add rate limiting | "The repository will add rate limiting" | No |
| Handle nil emails | "The repository will handle nil emails" | Yes |
| Implement caching | "The repository will implement caching" | No |
Developer-action verbs (add, implement, create, write, update, change) describe what the developer did. Repository-capability verbs (parse, handle, support, expose, enable, optimize, simplify, prevent, serialize, validate, extract) describe what the code does.
Quick Reference by Intent
| Intent | Verbs |
|---|---|
| New capability | handle, parse, transform, validate, serialize, cache, pool |
| Improvement | optimize, simplify, consolidate, enhance |
| Fix | fix, correct, respect, prevent |
| Structural | extract, expose, define, introduce |
| Removal | remove, drop, deprecate |
| Configuration | configure, enable, disable |
| Documentation | explain, clarify, document |
What ships with it
3 files 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.
- 7d ago First seen · 304 lines · 58 tokens per session scan A 2b690234a0dc
Writing Pull Requests is a skill published in the GitHub repository notorious-ai/claude-plugins (5 stars, last pushed 12d ago), licensed MIT. It adds 58 tokens to every session and 2,793 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-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…