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 sourav15mukherjee/skillforge-free-skills --skill pr-description-writergit clone --depth 1 https://github.com/sourav15mukherjee/skillforge-free-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/sourav15mukherjee/skillforge-free-skills/pr-description-writer)<a href="https://agentmods.dev/skills/sourav15mukherjee/skillforge-free-skills/pr-description-writer"><img src="https://agentmods.dev/badge/skills/sourav15mukherjee/skillforge-free-skills/pr-description-writer/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/sourav15mukherjee/skillforge-free-skills/pr-description-writer"><img src="https://agentmods.dev/badge/skills/sourav15mukherjee/skillforge-free-skills/pr-description-writer.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.00059 | $0.00458 |
| Opus 5 | $0.00030 | $0.00229 |
| Sonnet 5 | $0.00012 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
pr-description-writer 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 detailed, well-structured pull request descriptions by analyzing branch diffs.
Workflow
-
Identify branches Determine the current branch and the base branch (usually
mainormaster):git branch --show-current git log --oneline main..HEAD -
Analyze all changes Get the full diff and commit history:
git diff main...HEAD --stat git diff main...HEAD git log main..HEAD --format="%h %s" -
Categorize changes Group changes into logical categories:
- New features
- Bug fixes
- Refactoring
- Configuration changes
- Test additions/updates
- Documentation updates
-
Generate the PR description using this format:
## Summary
[1-3 sentences explaining the purpose and motivation]
## Changes
### [Category 1]
- Specific change with file reference
- Another change
### [Category 2]
- Change details
## Test Plan
- [ ] Manual testing step 1
- [ ] Manual testing step 2
- [ ] Automated tests pass
## Notes for Reviewers
[Any context that helps reviewers, areas of concern, or deployment notes]
Rules
- Always analyze ALL commits, not just the latest one
- Focus the summary on WHY, not WHAT
- Reference specific files when describing changes
- Include both manual and automated test steps
- Flag any breaking changes or migration requirements
- Keep the description scannable — use bullet points and headers
- If the PR is too large (>500 lines), suggest splitting it
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.
- 12d ago First seen · 77 lines · 59 tokens per session scan A 9adb39e46a9b
pr-description-writer is a skill published in the GitHub repository sourav15mukherjee/skillforge-free-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 458 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…