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 nimble-giant/nimble-mold --skill pr-descriptiongit clone --depth 1 https://github.com/nimble-giant/nimble-moldWrote 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/nimble-giant/nimble-mold/pr-description)<a href="https://agentmods.dev/skills/nimble-giant/nimble-mold/pr-description"><img src="https://agentmods.dev/badge/skills/nimble-giant/nimble-mold/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/nimble-giant/nimble-mold/pr-description"><img src="https://agentmods.dev/badge/skills/nimble-giant/nimble-mold/pr-description.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.00039 | $0.00494 |
| Opus 5 | $0.00019 | $0.00247 |
| Sonnet 5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-description
Generate a pull request description for the current branch changes.
Usage
/pr-description
Title
The title of the pr should adhere to our git conventional commit guidelines to make our titles consistent.
Description
This command generates a comprehensive PR description by comparing the current branch to the head of main using git diff main.... The PR description is saved as a markdown file in the /pr-descriptions folder.
If the /gh-issue command was used and the {{scm.provider}} issue for the branch is known, the PR description should begin with closes #<github-issue-number>.
Output
- Location:
/pr-descriptionsfolder - File naming:
pr-description-YYYY-MM-DD-HH-MM-SS.mdor descriptive name based on feature - Format: Markdown with clear section headers
Required Sections
Summary
Brief description of the PR purpose (1-3 sentences)
Changes
List of specific changes made (bullet points)
UAT
Instructions for how to test the changes
Example Structure
# feat(web): add control families to compliance section
closes #1234
## Summary
This PR adds support for Control Families in the Judge web UI, allowing users to organize compliance controls into logical groupings. Control families create a hierarchy between frameworks and controls.
## Changes
- Added Control Families menu item in Compliance section
- Created new page and components for viewing/managing control families
- Added family column to Controls table
- Updated GraphQL queries to include control family information
- Added hooks for querying, creating, and updating control families
## UAT
1. Navigate to Compliance > Families
2. Create a new control family
3. Create a control and assign it to the family
4. Verify the control shows up in the family's detail page
Notes
- Only generate when explicitly requested with
/pr-descriptionor when directly asked to "create a PR description" - Always compare current branch to main branch for complete context
- Do not include AI attribution or generated-by notices in PR descriptions
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 · 74 lines · 39 tokens per session scan A 5fd955230e16
pr-description is a skill published in the GitHub repository nimble-giant/nimble-mold (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 494 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.