Borrowing it
Nothing to install: this file belongs to thomaspinder/Impulso. 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/thomaspinder/Impulso/main/.claude/commands/pr.mdgit clone --depth 1 https://github.com/thomaspinder/ImpulsoWrote 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/thomaspinder/impulso/pr)<a href="https://agentmods.dev/commands/thomaspinder/impulso/pr"><img src="https://agentmods.dev/badge/commands/thomaspinder/impulso/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/thomaspinder/impulso/pr"><img src="https://agentmods.dev/badge/commands/thomaspinder/impulso/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.00000 | $0.00510 |
| Opus 5.5 | $0.00000 | $0.00204 |
| Sonnet 5.5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
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.
This is a copy
100% identical to pr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr — Create a PR summarising changes vs main
Analyse the diff between the current branch and main, then open a pull request using the GitHub CLI (gh).
Steps
- Run
git diff main...HEADto get the full diff. - Run
git log main..HEAD --onelineto get the commit list. - Analyse the diff and commits to understand the nature of the changes.
- Classify the change into exactly one primary category and assign the corresponding label:
| Category | PR title prefix | GitHub label |
|---|---|---|
| New feature | feat: |
enhancement |
| Bug fix | fix: |
bug |
| Breaking change | feat!: / fix!: |
breaking-change |
| Documentation | docs: |
documentation |
| Refactor | refactor: |
internal |
| Testing | test: |
internal |
| Chore / CI | chore: |
internal |
| Performance | perf: |
performance |
-
Write the PR title in imperative mood with the appropriate prefix.
-
Write the PR body using this structure:
Body
## Summary
2–3 sentences: what this PR does and why.
## Changes
- Key changes grouped logically (not one per file).
## Testing
How changes were tested, or note if tests are included.
## Notes
Breaking changes, migration steps, deprecations, or follow-ups.
-
Request feedback from me around the PR title and body before creating the PR. I may ask for revisions to ensure clarity and completeness.
-
Only once you have my approval, create the PR:
gh pr create \
--title "<prefix>: <title>" \
--body "<body>" \
--label "<label>"
If the label doesn't exist yet, create it first with gh label create.
Rules
- Do NOT fabricate changes — only describe what is in the diff.
- Always assign exactly one category label.
- If the change is breaking, mention it explicitly in the Summary and Notes sections.
- If the diff is empty, stop and inform me.
- If
ghis not authenticated, tell me to rungh auth login.
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 · 59 lines · 0 tokens per session scan A 6b3b41905496
pr is a command published in the GitHub repository thomaspinder/Impulso (25 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 510 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pr, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
codex-review
Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.