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 agentmods add skills/jnmetacode/skillet/pr-descriptionnpx skills add jnMetaCode/skillet --skill pr-descriptiongit clone --depth 1 https://github.com/jnMetaCode/skilletWrote 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/jnmetacode/skillet/pr-description)<a href="https://agentmods.dev/skills/jnmetacode/skillet/pr-description"><img src="https://agentmods.dev/badge/skills/jnmetacode/skillet/pr-description.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.00031 | $0.00499 |
| Opus 5 | $0.00015 | $0.00249 |
| Sonnet 5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
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 6d 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
The reader is a reviewer deciding how to review, not a historian. Write from the diff, not from memory of the conversation.
Procedure
- Establish the real change set:
git log main..HEAD --onelineandgit diff main...HEAD --stat. Read the diff of every file a reviewer will question. - Open with one sentence of why — the problem or goal, not the activity ("Checkout fails for SSO users" beats "Update auth flow").
- What changed, grouped by intent rather than by file: behavior changes first, then refactors, then mechanical churn (renames, formatting) called out explicitly so reviewers can skim past it.
- How to verify: the exact commands/steps you ran and their result. If CI covers it, say which jobs; if manual, give the click-path.
- Risk and rollout: what could break, feature flags, migrations, revert plan. One line each. Omit the section only if genuinely none.
- Call out anything you want focused review on ("the locking in store.js is the risky part") — reviewers allocate attention where the author points.
Anti-patterns
- Restating the commit list — the PR already shows it.
- "See ticket" as the why — summarize the ticket in one line, then link it.
- Screenshots without a caption saying what to look at.
- Describing the diff file-by-file — group by intent.
Skeleton
Fixes checkout failing for SSO users (#412).
**What**
- Treat IdP-initiated sessions as authenticated in the cart guard (behavior)
- Extract session checks into `session.ts` (refactor, no behavior change)
**Verify**: `npm test` (all green) + manual SSO login → add to cart → checkout.
**Risk**: session guard touches every authed route; revert is a single commit.
Focus review on `session.ts:40-75`.
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.
- 6d ago First seen · 52 lines · 31 tokens per session scan A f0e4ebbddaaa
pr-description is a skill published in the GitHub repository jnMetaCode/skillet (1 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 499 once invoked, about $0.0002 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
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
pull-request-automation
Audits and improves the pull request workflow for a GitHub repository. Covers PR description templates, auto-labelling, CODEOWNERS, PR size checks, and branch protection rules. Invoked when the user asks to improve the PR process, set up PR automation, or add a PR template.
changelog-generator
Transform technical git commits into polished, user-friendly changelogs and release notes. Automatically categorizes changes, translates developer language into customer-friendly copy, and generates professional changelog entries.
github
GitHub workflow — creating and managing repos, always working on feature/development branches (never committing core changes directly to main), PR conventions, branch protection, and gh CLI patterns.
code-reviewer
按专业标准审查代码变更，关注正确性、安全性、可维护性和性能.