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 tonyghiani/ai-essentials --skill pr-description-templategit clone --depth 1 https://github.com/tonyghiani/ai-essentialsWrote 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/tonyghiani/ai-essentials/pr-description-template)<a href="https://agentmods.dev/skills/tonyghiani/ai-essentials/pr-description-template"><img src="https://agentmods.dev/badge/skills/tonyghiani/ai-essentials/pr-description-template.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.00063 | $0.00507 |
| Opus 5 | $0.00032 | $0.00253 |
| Sonnet 5 | $0.00013 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
pr-description-template 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.
What it actually says
PR Description Template
When to use
Use this skill when the user asks for:
- a PR description
- a PR body for GitHub
- a summary/testing section for a pull request
Output requirements
Always follow these rules:
- Keep heading icons as part of the heading text (example:
## 📓 Summary,## 🧪 Testing). - Write the summary as a mix of short paragraphs and bullet points.
- Keep the title concise and focused on the main change.
- Keep testing steps actionable and reproducible.
Template
Use this exact structure:
> <concise PR title summarizing the main change>
## 📓 Summary
<2-4 sentences explaining what the PR does, why it is needed, and the outcome. Mention impacted area(s) and context.>
- <key change 1>
- <key change 2>
- <key change 3>
## 🧪 Testing
- <main flow to test>
- <edge case or secondary flow>
- <validation check (errors, telemetry, or regressions)>
Writing guidance
- Prefer concrete wording over generic phrasing.
- Mention affected layers explicitly when relevant (API, UI, background jobs, telemetry, tests).
- Keep bullets parallel and one line when possible.
- Do not include unrelated implementation detail.
Output
Return only the formatted PR description text. Do not offer to create the PR, run gh, or ask about a base branch.
Example
> Add retry with exponential backoff to payment webhook handler
## 📓 Summary
Webhook deliveries to our payment provider occasionally fail on transient network errors. This change adds bounded retries so successful payments are not lost when the first POST times out.
- Adds retry helper with exponential backoff and jitter.
- Applies retries only to idempotent webhook dispatch paths.
- Logs each retry attempt with correlation id for debugging.
## 🧪 Testing
- Simulate network timeout and confirm webhook succeeds on retry.
- Verify non-idempotent endpoints still fail fast without retry.
- Check logs include attempt count and final outcome.
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 First seen · 70 lines · 63 tokens per session scan A 6898a4227593
pr-description-template is a skill published in the GitHub repository tonyghiani/ai-essentials (6 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 507 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…