Borrowing it
Nothing to install: this file belongs to pyrex41/skill-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pyrex41/skill-manager/master/.claude/commands/cl/describe_pr.mdgit clone --depth 1 https://github.com/pyrex41/skill-managerWrote 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/pyrex41/skill-manager/describe_pr)<a href="https://agentmods.dev/commands/pyrex41/skill-manager/describe_pr"><img src="https://agentmods.dev/badge/commands/pyrex41/skill-manager/describe_pr/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/commands/pyrex41/skill-manager/describe_pr"><img src="https://agentmods.dev/badge/commands/pyrex41/skill-manager/describe_pr.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.00007 | $0.00574 |
| Opus 5.5 | $0.00003 | $0.00230 |
| Sonnet 5.5 | $0.00001 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
describe_pr 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 2mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate PR Description
You are tasked with generating a comprehensive pull request description.
Process
Step 1: Identify the PR
- Check if current branch has a PR:
gh pr view --json url,number,title,state 2>/dev/null - If no PR exists, list open PRs:
gh pr list --limit 10 --json number,title,headRefName,author - Ask which PR to describe if unclear
Step 2: Gather PR Information
- Get the full PR diff:
gh pr diff {number} - Get commit history:
gh pr view {number} --json commits - Get PR metadata:
gh pr view {number} --json url,title,number,state,baseRefName
Step 3: Analyze Changes Thoroughly
- Read through the entire diff carefully
- For context, read files referenced but not in the diff
- Understand the purpose and impact of each change
- Identify:
- User-facing changes vs. internal implementation
- Breaking changes or migration requirements
- New dependencies or configurations
Step 4: Run Verification
For any verification commands you can run:
- If it passes, mark checkbox:
- [x] - If it fails, keep unchecked with explanation:
- [ ] - If it requires manual testing, leave unchecked and note for user
Step 5: Generate Description
Create a comprehensive description:
## Summary
[2-3 sentences describing what this PR does and why]
## Changes
### [Category 1]
- Change description
- Another change
### [Category 2]
- Change description
## Breaking Changes
[List any breaking changes, or "None"]
## How to Verify
### Automated
- [x] `make check` passes
- [x] `make test` passes
- [ ] [Test that couldn't be run - reason]
### Manual
- [ ] [Manual verification step 1]
- [ ] [Manual verification step 2]
## Related
- Fixes #[issue number] (if applicable)
- Related to #[other PR] (if applicable)
Step 6: Update the PR
- Update the PR description:
gh pr edit {number} --body-file [description file] - Confirm the update was successful
- Remind user of any unchecked verification steps
Important Notes
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.
- 2mo ago First seen · 93 lines · 7 tokens per session scan A b2915c96c804
describe_pr is a command published in the GitHub repository pyrex41/skill-manager (4 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 574 once invoked, about $0.0000 per session on Opus 5.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.
describe_pr compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| describe_prpyrex41/skill-manager | Command | 4 | 9mo ago | MIT | A | 7 | Claude Code |
| standupvvedantb/eva | Command | 101 | yesterday | MIT | A | 0 | Claude Code |
| gitazrtydxb/procoder | Command | 211 | 11d ago | Apache-2.0 | A | 20 | Claude Code |
| session-reportdamusix/atomic-claude | Command | 115 | 5d ago | MIT | A | 31 | Claude Code |
| commitechoVic/blade-code | Command | 181 | 24d ago | MIT | A | 8 | Claude Code |
| git-workflowHermeticOrmus/LibreUIUX-Claude-Code | Command | 115 | 1mo ago | MIT | A | 14 | Claude Code |
| commitjoaquimscosta/arkhe-claude-plugins | Command | 22 | 22d ago | MIT | A | 11 | Claude Code |