Borrowing it
Nothing to install: this file belongs to bliporg/blip. 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/bliporg/blip/main/.claude/commands/pr.mdgit clone --depth 1 https://github.com/bliporg/blipWrote 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/bliporg/blip/pr)<a href="https://agentmods.dev/commands/bliporg/blip/pr"><img src="https://agentmods.dev/badge/commands/bliporg/blip/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/bliporg/blip/pr"><img src="https://agentmods.dev/badge/commands/bliporg/blip/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.00334 |
| Opus 5.5 | $0.00000 | $0.00134 |
| Sonnet 5.5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade C, and why
pr scanned grade C with 1 finding 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 1mo 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
Check issues using GitHub CLI to see if some Fixes #ISSUE-NUMBER or Contributes to #ISSUE-NUMBER could be added. Always put those statements at the very top of the description. Do not include TODO lists, unless e What it actually says
Open or update PR
I want to make sure there's a PR that's in a good state for the local branch.
If there are local changes (not yet committed), ask if you should commit those changes, discard them, or do things differently. You'll need an answer before continuing.
Now if there are no local changes:
Git fetch and make sure the branch is rebased against origin/main. Rebase the branch against origin/main if not, fixing conflicts if needed. Ask if you're unsure about how some conflicts should be solved.
Now if the branch is correctly rebased against origin/main:
Please use Git CLI to check if there's already a PR for this branch and create it otherwise.
Use git diff origin/main..HEAD to get the complete diff from origin/main.
Use the diff to set a great title that describes the content of the PR, the main problem it's addressing. If there's already a title or description, make sure it covers diff changes, don't hesitate to update them if needed.
The description should be no longer than 50 lines, the shorter the better (it's ok if it's one line).
Check issues using GitHub CLI to see if some Fixes #ISSUE-NUMBER or Contributes to #ISSUE-NUMBER could be added. Always put those statements at the very top of the description.
Do not include TODO lists, unless explicitly requested. Do not erase existing TODO lists.
Do not run any CI tests locally. The PR might not be fully ready for review, and that's ok.
Always post the PR URL and branch name at the end of your work.
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.
- 1mo ago First seen · 28 lines · 0 tokens per session scan C 0df07331051c
pr is a command published in the GitHub repository bliporg/blip (286 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 334 tokens. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other commands, from other repositories
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
release-tag
Create and push a version tag after a release PR has been merged.