Borrowing it
Nothing to install: this file belongs to bakabaka91/claude-baton. 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/bakabaka91/claude-baton/main/.claude/commands/pr.mdgit clone --depth 1 https://github.com/bakabaka91/claude-batonWrote 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/bakabaka91/claude-baton/pr)<a href="https://agentmods.dev/commands/bakabaka91/claude-baton/pr"><img src="https://agentmods.dev/badge/commands/bakabaka91/claude-baton/pr.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.00241 |
| Opus 5 | $0.00000 | $0.00120 |
| Sonnet 5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
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 4d 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
Prepare and create a pull request.
Steps
-
Pre-flight checks:
- Run
git statusto see all changes - Run
git diffto review what changed - Verify no secrets or credentials in changed files
- Run
-
Run tests:
- Run
npm run build— must compile clean - Run
npm test— all tests must pass - If either fails, fix issues before proceeding
- Run
-
Run lint:
- Run
npx eslint src/ tests/ --ext .ts - Run
npx prettier --check "src/**/*.ts" "tests/**/*.ts" - Auto-fix if needed, then re-check
- Run
-
Constraints verification:
- No new dependencies beyond the 4 allowed
- No anthropic SDK imports
- No native SQLite bindings
- No SSE transport code
- No git branch manipulation in source code
-
Create PR:
- Stage relevant files
- Create commit with descriptive message
- Push branch
- Create PR with summary, test plan, and constraints 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.
- 4d ago First seen · 32 lines · 0 tokens per session scan A 3f3473686f3a
pr is a command published in the GitHub repository bakabaka91/claude-baton (25 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 241 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
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
智能生成 Git 提交信息并提交.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
changelog
Summarize staged git changes into a concise changelog/commit message.