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 lucianghinda/agentic-skills --skill pr-descriptiongit clone --depth 1 https://github.com/lucianghinda/agentic-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/lucianghinda/agentic-skills/pr-description)<a href="https://agentmods.dev/skills/lucianghinda/agentic-skills/pr-description"><img src="https://agentmods.dev/badge/skills/lucianghinda/agentic-skills/pr-description/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/lucianghinda/agentic-skills/pr-description"><img src="https://agentmods.dev/badge/skills/lucianghinda/agentic-skills/pr-description.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.00050 | $0.00491 |
| Opus 5 | $0.00025 | $0.00246 |
| Sonnet 5 | $0.00010 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
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 12d 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 Writer
Generate structured PR descriptions from branch commits.
Workflow
- Get commits:
git log --oneline origin/main..HEAD(fallback toHEAD~10..HEAD) - Get each commit's details:
git show <hash> --stat --format="%H%n%s%n%b" - Get each commit's diff:
git diff <hash>^..<hash> - Write PR description following the output format below
Output Format
1. Title
Single line. Use most meaningful commit subject or synthesize one. Keep short and technical.
2. Summary (2-5 bullets)
High-level changes. Each bullet concrete and verifiable.
3. Why (1-4 bullets)
Motivation, problem, or user impact. Tie to reliability, security, performance, DX, or product needs.
4. Commit-by-commit details
For EACH commit, add subsection with exact subject as heading:
What: 1-3 bullets describing concrete changes
Why: 1-2 bullets explaining motivation/tradeoffs
Notes: (optional) only for risk, migration, follow-up, or nuance
Rules:
- Preserve commit subject exactly as written
- If commit has a meaningful description use that
- If commit is noisy (formatting, rename), say so briefly
- Related commits: document each, keep later ones shorter ("follow-up", "fixup")
5. Testing
Checklist of what was done. If none provided, infer likely checks and label "Suggested".
6. Risk and rollout (2-6 bullets)
- What could break
- Where to watch
- Rollback plan (1 line)
- If breaking change, include BREAKING CHANGE callout
7. Screenshots/logs (optional)
Only if UI, behavior, or observability changed.
Style
- Direct and technical. No marketing tone.
- No fluff or jokes.
- Short sentences. Prefer bullets over paragraphs.
- Do not invent facts. Say "Likely" or "Inferred" if uncertain.
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.
- 12d ago First seen · 62 lines · 50 tokens per session scan A 7d8e8c59bc7e
pr-description is a skill published in the GitHub repository lucianghinda/agentic-skills (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 491 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…