Borrowing it
Nothing to install: this file belongs to princeton-ddss/blackfish. 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/princeton-ddss/blackfish/main/.claude/commands/pr-checklist.mdgit clone --depth 1 https://github.com/princeton-ddss/blackfishWrote 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/princeton-ddss/blackfish/pr-checklist)<a href="https://agentmods.dev/commands/princeton-ddss/blackfish/pr-checklist"><img src="https://agentmods.dev/badge/commands/princeton-ddss/blackfish/pr-checklist.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.1 | $0.00000 | $0.00246 |
| Opus 5 | $0.00000 | $0.00123 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
pr-checklist 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.
What it actually says
Output the PR checklist for the contributor to review before creating a pull request.
PR Checklist
Before creating a pull request, ensure you have completed the following:
Code Quality
- Code follows project conventions and patterns
- No debug statements or commented-out code
Testing
- Tests pass locally
- Python:
cd lib && uv run just test - Frontend:
cd web && npm test
- Python:
- New functionality has test coverage
- Linting passes
- Python:
cd lib && uv run just lint - Frontend:
cd web && npm run lint
- Python:
Documentation
- Code is self-documenting or has necessary comments
- README updated if adding new features or changing setup
Coverage Badge (Python changes only)
- Coverage badge updated:
cd lib && uv run just coverage - Badge changes committed
Final Steps
- Commits are clean and have clear messages
- Branch is up to date with main
- PR title and description are clear
Use /pr to create the pull request after completing this checklist.
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 · 34 lines · 0 tokens per session scan A f1c145c97977
pr-checklist is a command published in the GitHub repository princeton-ddss/blackfish (24 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 246 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-09-01.
Other commands, from other repositories
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
build
Implement the next task incrementally — build, test, verify, commit.
quick
Role: Minimal-ceremony feature workflow for solo developers and small changes. Implement → test → commit. No PRD required, no full pipeline overhead.
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.