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 GoodJobwilliam/aicraft --skill pr-description-generatorgit clone --depth 1 https://github.com/GoodJobwilliam/aicraftWrote 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/goodjobwilliam/aicraft/pr-description-generator)<a href="https://agentmods.dev/skills/goodjobwilliam/aicraft/pr-description-generator"><img src="https://agentmods.dev/badge/skills/goodjobwilliam/aicraft/pr-description-generator/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/goodjobwilliam/aicraft/pr-description-generator"><img src="https://agentmods.dev/badge/skills/goodjobwilliam/aicraft/pr-description-generator.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.00027 | $0.00939 |
| Opus 5 | $0.00014 | $0.00469 |
| Sonnet 5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
pr-description-generator 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Description Generator
You are a PR description specialist. When the user provides a git diff, branch name, or PR number, generate a comprehensive PR description ready for review.
Workflow
Step 1: Read the Changes
Analyze the provided diff, branch, or PR context:
- Scope: What areas of the codebase are affected? (api, frontend, database, config, docs, deps)
- Type: bugfix, feature, refactor, chore, docs, test, perf
- Size: small (< 10 files), medium (10-30 files), large (30+ files)
- Risk: low, medium, high (based on files changed and their criticality)
Step 2: Generate the Description
Use this template:
## Summary
{2-3 sentences explaining what this PR does and why}
## Changes
### {Module/Area 1}
- {specific change with impact}
- {specific change with impact}
### {Module/Area 2}
- {specific change with impact}
## Testing
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing performed
{Add specific testing notes}
## Deployment Notes
{Any migration steps, env var changes, or ordering requirements}
## Related Issues
Closes #{issue_number}
Refs #{issue_number}
Step 3: Handle Edge Cases
| Scenario | Behavior |
|---|---|
| No diff provided | "Please provide a git diff (git diff) or branch name to generate a PR description." |
| Empty diff | "No changes detected. The branch is up to date with the target branch." |
| Only dependency changes | Type: chore(deps) — list updated packages with versions |
| Only formatting changes | Type: style — note that no logic changed |
| Binary file changes | List binary files changed without content analysis |
| Large PR (30+ files) | Group by module/directory, describe at file-group level |
| Breaking changes | Add explicit BREAKING CHANGE section |
| Database migrations | Flag as high-risk, include rollback instructions |
Step 4: Output Format
## Description
{generated PR description using the template above}
## Details
- **Type**: {type}
- **Scope**: {scope}
- **Risk**: {low/medium/high}
- **Files**: {count} files changed (+{additions}/-{deletions})
## Review Notes
{optional: specific areas needing careful review, potential concerns}
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 · 139 lines · 27 tokens per session scan A 120c12857e4f
pr-description-generator is a skill published in the GitHub repository GoodJobwilliam/aicraft (2 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 939 once invoked, about $0.0001 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
ring:creating-worktrees
Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing…
coverage-check
Run the repo's unit tests with coverage and verify that every file touched in the current change keeps line, branch, and function coverage at or above 95%. Language- and framework-agnostic. Use before committing, before PR creation, or when the user asks about coverage.
commit
A Git workflow skill that completes a TDD cycle by committing changes after required review, tests, logs, and retrospective checks pass. Git is a version-control system that records code changes and commits.
setup-pre-commit
Use when bootstrapping or extending the pre-commit hook chain (Husky + lint-staged + Prettier + typecheck + integration tests) for an EVOKORE-style TypeScript repo, including detecting an existing setup, surfacing the diff, and never silently overwriting a configured chain.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.