Borrowing it
Nothing to install: this file belongs to bobbylight/AutoComplete. 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/bobbylight/AutoComplete/master/.claude/commands/pr.mdgit clone --depth 1 https://github.com/bobbylight/AutoCompleteWrote 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/bobbylight/autocomplete/pr)<a href="https://agentmods.dev/commands/bobbylight/autocomplete/pr"><img src="https://agentmods.dev/badge/commands/bobbylight/autocomplete/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.00736 |
| Opus 5 | $0.00000 | $0.00368 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
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 yesterday.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Pull Request
Create a branch (if needed), commit staged/unstaged changes, push, and open/update a PR.
Steps
-
Check branch status: Run
git statusandgit branch --show-current- If on
masterormain, create a new branch:- Analyze the changes to determine a descriptive branch name
- Use lower-kebab-case (e.g.,
add-user-authentication,fix-login-bug) - Run
git checkout -b <branch-name>
- If already on a feature branch, continue on that branch
- If on
-
Ensure JDK 25 is on the path. This library requires JDK 25 or later to build. Ensure that
java --versionshows25or later. If not, search for Java 25 in common locations for the operating system. If you can't find it, exit early. -
Build locally by running
./gradlew clean build. If there are any checkstyle or spotbugs failure, or javac errors, fix them and rerun this check to verify your changes. Don't worry about javac warnings currently - there are 3 that we need to address later, but for now can be ignored. -
Review changes: Run
git statusandgit diffto understand what will be committed -
Stage and commit:
- Stage relevant files (prefer specific files over
git add -A) - Determine the commit strategy:
- If the feature branch has no prior commits: create a new commit
- If the feature branch has a prior commit and a draft PR exists (
gh pr view --json isDraft): amend the existing commit (git commit --amend) - If the feature branch has a prior commit and no PR exists, or the PR is not in draft: create a new commit
- Write a commit message (or update the existing one if needed) using the conventional commit style
- Don't read the conventional commit site/URL if you already know the style
- Use "!" after the type to indicate a breaking change
- Use "build(deps)" for dependency bumps
- Include
Co-Authored-By: Claude <[email protected]>in the commit message
- Stage relevant files (prefer specific files over
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.
- yesterday First seen · 51 lines · 0 tokens per session scan A 31d1bc567332
pr is a command published in the GitHub repository bobbylight/AutoComplete (184 stars, last pushed 10d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 736 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-04.
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.