Borrowing it
Nothing to install: this file belongs to sunnykgupta/AI-Helpers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sunnykgupta/AI-Helpers/main/.opencode/skills/pr-description/SKILL.mdgit clone --depth 1 https://github.com/sunnykgupta/AI-HelpersWrote 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/sunnykgupta/ai-helpers/pr-description)<a href="https://agentmods.dev/skills/sunnykgupta/ai-helpers/pr-description"><img src="https://agentmods.dev/badge/skills/sunnykgupta/ai-helpers/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/sunnykgupta/ai-helpers/pr-description"><img src="https://agentmods.dev/badge/skills/sunnykgupta/ai-helpers/pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.00418 |
| Opus 5 | $0.00042 | $0.00209 |
| Sonnet 5 | $0.00017 | $0.00084 |
| Haiku 4.5 | $0.00008 | $0.00042 |
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 10d 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
Write clear, reviewable GitHub PR descriptions.
Format
## What
One or two sentences. What does this PR change?
## Why
The problem or motivation. Link the issue if there is one (`Fixes #123`).
## How
Bullet points of the main implementation choices. Skip if the change is trivial.
## Testing
How it was verified. "Added unit tests", "Manually tested on staging", etc.
## Notes for reviewers
Optional. Call out anything non-obvious, risky, or that needs extra eyes.
Omit any section that has nothing useful to say.
Rules
- Keep
## Whatunder 2 sentences. Reviewers scan this first. - Link issues with
Fixes #NorCloses #Nso GitHub auto-closes them on merge. - Prefer bullets over paragraphs in
## How. - Never just list files changed — reviewers can see the diff. Explain decisions.
- If the diff touches public APIs, call it out explicitly under
## Notes for reviewers. - Match the repo's existing PR tone if visible (formal vs casual).
Workflow
- If a
.github/PULL_REQUEST_TEMPLATE.mdexists in the repo, use it as the structure instead of the default above. - Read the diff or commit list. Ask for it if not provided.
- Draft the PR body. Keep it under ~150 words unless the change is large.
- If there are breaking changes, put a Breaking change line at the top.
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.
- 10d ago First seen · 45 lines · 84 tokens per session scan A b56a60b6c070
pr-description is a skill published in the GitHub repository sunnykgupta/AI-Helpers (70 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 418 once invoked, about $0.0004 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-30.
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.
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…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.