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 jamesyang124/agent-skills --skill generate-pr-notesgit clone --depth 1 https://github.com/jamesyang124/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/jamesyang124/agent-skills/generate-pr-notes)<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/generate-pr-notes"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/generate-pr-notes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/generate-pr-notes"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/generate-pr-notes.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02741 |
| Opus 5.5 | $0.00000 | $0.01096 |
| Sonnet 5.5 | $0.00000 | $0.00548 |
| Haiku 4.5 | $0.00000 | $0.00274 |
Grade A, and why
generate-pr-notes 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 8d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate PR Notes
Install this skill globally
Install once — available in all projects.
# Claude (copy the whole folder: the PR template lives in references/)
mkdir -p ~/.claude/skills
cp -R <agent-settings-repo>/.agent-settings/skills/tools/generate-pr-notes ~/.claude/skills/
# Add to ~/.claude/CLAUDE.md: - **generate-pr-notes** (`~/.claude/skills/generate-pr-notes/SKILL.md`)
# Copilot
mkdir -p ~/.copilot/skills
cp -R <agent-settings-repo>/.agent-settings/skills/tools/generate-pr-notes ~/.copilot/skills/
Or link it with .agent-settings/skills/import-skills.sh --global claude generate-pr-notes.
Dependencies
No external skills or MCPs required. Requires git to be available in the shell.
Automatically generate pull request notes based on git changes.
Description
This skill analyzes git changes and generates comprehensive pull request notes. It can work with either a single commit or all changes in the current branch compared to the main/master branch.
Usage
/generate-pr-notes
Arguments
All optional.
| Token | Meaning |
|---|---|
a branch name (e.g. develop) |
base branch to diff against — skips the base-branch question in step 1 |
Scope (last commit vs. entire branch) is always asked; it is not an argument.
Instructions
Use the Task tool with subagent_type="general-purpose" to spawn an agent that will generate pull request notes. Pass the following instructions to the agent.
CRITICAL: After the agent completes, follow these steps IN ORDER:
-
Output verbatim — display the agent's full response exactly as returned in the terminal. Do NOT summarize or modify it.
-
Extract content — strip the outer
```markdownopening fence and the closing```fence from the agent output to get the raw markdown text only. -
Determine output path — before writing, run these two commands via Bash:
- Repo name:
basename $(git rev-parse --show-toplevel) - Short hash:
git rev-parse --short HEADConstruct the output path as/tmp/pr-notes-<repo-name>-<short-hash>.md(e.g./tmp/pr-notes-agent-skills-a1b2c3d.md). Use the Write tool to save the extracted markdown to that path.
- Repo name:
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.
- 8d ago Changed · -28 lines · -66 tokens per session 1d3de475230b
- 1mo ago First seen · 234 lines · 66 tokens per session scan A 29ed7a0b6bbd
generate-pr-notes is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,741 tokens. 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.