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/kimgoetzke/coding-agent-configs/generate-pr-descriptionnpx skills add kimgoetzke/coding-agent-configs --skill generate-pr-descriptiongit clone --depth 1 https://github.com/kimgoetzke/coding-agent-configsWrote 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/kimgoetzke/coding-agent-configs/generate-pr-description)<a href="https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/generate-pr-description"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/generate-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.1 | $0.00032 | $0.00836 |
| Opus 5 | $0.00016 | $0.00418 |
| Sonnet 5 | $0.00006 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
generate-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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate PR description
Generate the PR description without wrapping it in a code fence. Never post or edit it unless authorised under 4. Decide whether to update the PR.
1. Establish the change
- If given a PR number or URL, inspect its metadata, commits, and full diff.
- Otherwise, inspect the PR associated with the current branch. If none exists, compare the current branch with the repository's default branch, including committed changes only.
- Read enough surrounding code and documentation to understand behaviour rather than merely restating file changes.
- Derive motivation from reliable context such as the PR, linked issue, commit messages, or repository documentation. Never invent motivation. If it remains unclear, ask one focused question before drafting.
2. Select content
What
Describe outcomes and observable behaviour, not the editing process.
- Use 1–5 bullets; target at most 15 words each.
- Keep one distinct change per bullet and group closely related implementation details.
- Prefer product or user-facing behaviour over file names and implementation mechanics.
- Include internal changes only when they are the substance of the PR or materially affect maintainers.
- Omit tests, formatting, generated files, routine wiring, and incidental refactors from feature or fix PRs.
- If the PR only changes tests, describe those test changes.
- Do not claim behaviour unsupported by the diff.
Why
Write at most one extremely succinct sentence explaining the problem, need, or motivation. Do not repeat the What section.
Notes
Omit this section by default. Add it only when critical understanding requires one of:
- stating that something was deliberately not done;
- explaining why something was skipped;
- providing essential context not suitable for What or Why.
Use no more than three succinct bullets. Do not add routine test, deployment, or implementation commentary.
3. Output
Use this exact structure, omitting ### Notes entirely when unnecessary:
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 · 104 lines · 32 tokens per session scan A 439eecdbea32
generate-pr-description is a skill published in the GitHub repository kimgoetzke/coding-agent-configs (2 stars, last pushed 16d ago), licensed MIT. It adds 32 tokens to every session and 836 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
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
write-commit-message
Writes high-quality git commit messages following the seven rules of great commit messages (Chris Beams) and a fixed subject+body template. Auto-triggers whenever a commit is being authored or suggested — e.g. the user asks to "commit", "commit this", "git commit", or the agent itself is about to run git commit — not…
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-commit-push-pr
Commit all changes, push to remote, and open a pull request in one go. Use when the user says "commit push pr", "ship it", "open a pr", or invokes /git-commit-push-pr.