Borrowing it
Nothing to install: this file belongs to wbern/agent-instructions. 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/wbern/agent-instructions/main/.claude/commands/pr-show.mdgit clone --depth 1 https://github.com/wbern/agent-instructionsWrote 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/wbern/agent-instructions/pr-show)<a href="https://agentmods.dev/commands/wbern/agent-instructions/pr-show"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/pr-show/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/wbern/agent-instructions/pr-show"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/pr-show.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.00019 | $0.00887 |
| Opus 5.5 | $0.00008 | $0.00355 |
| Sonnet 5.5 | $0.00004 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
pr-show 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show - Visible Merge with Optional Feedback
General Guidelines
Output Style
- Never explicitly mention TDD in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use mcp__beads__* tools to manage issues (the user interacts via bd commands).
Plan File Restriction
NEVER create, read, or update plan.md files. Claude Code's internal planning files are disabled for this project. Use other methods to track implementation progress (e.g., comments, todo lists, or external tools).
Ship/Show/Ask Pattern - SHOW
Show is for changes that teammates should see, but don't require approval. Examples:
- Refactoring with test coverage
- New features with comprehensive tests
- Performance improvements
- Non-breaking API changes
Prerequisites
Before using show:
- All tests must pass
- Changes should have good test coverage
- Changes should be non-breaking or backward compatible
- CI must be green
Workflow
Current branch status:
!git status
Recent commits:
!git log --oneline -5
User arguments:
Show: $ARGUMENTS
End of user arguments
Process:
-
Verify Quality: Check that changes meet show criteria
- Run tests: !
npm testor !yarn testor appropriate test command - Check coverage is maintained or improved
- Verify no breaking changes
- Run tests: !
-
Create Show PR: Create a PR that will auto-merge after a short window
- Title: conventional commits format, prefixed with
[SHOW] - Description: Clear explanation of what changed and why
- Add label: "show" or "auto-merge"
- Set auto-merge if GitHub setting allows
- Title: conventional commits format, prefixed with
-
Configure Auto-Merge:
- If GitHub Actions is configured, set to auto-merge after CI passes
- If not, provide instructions to merge after 1-2 hours of visibility
- Add notice that feedback is welcome but not required
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 · 134 lines · 19 tokens per session scan A 496f2fb6d55d
pr-show is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 887 once invoked, about $0.0001 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-30.
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.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
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.