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 commands/nimble-giant/ailloy/pr-descriptiongit clone --depth 1 https://github.com/nimble-giant/ailloyWrote 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/commands/nimble-giant/ailloy/pr-description)<a href="https://agentmods.dev/commands/nimble-giant/ailloy/pr-description"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/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 | $0.00000 | $0.00455 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 5d 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 — 70 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
claude 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 Claude knows what GitHub issue the branch is for, 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
claude pr-description,/pr-description, or when directly asked to "create a PR description" - Always compare current branch to main branch for complete context
- Do not include Claude Code 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.
- 5d ago First seen · 70 lines · 0 tokens per session scan A fbb7f9549f98
pr-description is a command published in the GitHub repository nimble-giant/ailloy (10 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 455 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.