Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/llcoolblaze/claude-boris/commit-push-prgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWhat 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 | $0.00021 | $0.00340 |
| Opus 5 | $0.00010 | $0.00170 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
commit-push-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 3d 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
Git Context
!git status --short
!git branch --show-current
!git log -3 --oneline
!git diff --stat
Based on the changes above, execute the full git workflow:
1. Stage Changes
Stage all modified files appropriately.
2. Commit
Create a commit with a conventional commit message:
feat:- New featurefix:- Bug fixdocs:- Documentation onlystyle:- Formatting, no code changerefactor:- Code change that neither fixes nor addsperf:- Performance improvementtest:- Adding testschore:- Maintenance, deps, config
Format: type(scope): description
Keep the first line under 72 characters. Add a body if the change needs explanation.
3. Push
Push to the remote repository. Create the remote branch if needed.
4. Create PR
Use gh pr create to open a pull request with:
- Clear, descriptive title
- Body explaining what changed and why
- Link to related issues if applicable
gh pr create --title "type(scope): description" --body "## Summary
- What was done
- Why it was done
## Testing
- How it was tested
## Related
- Closes #123 (if applicable)"
If there are no changes to commit, inform the user and suggest next steps.
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.
- 3d ago First seen · 55 lines · 21 tokens per session scan A 75eca3a65078
commit-push-pr is a command published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 340 once invoked, about $0.0001 per session on Opus 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
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.
commit
Based on the above changes, create a single git commit.
commit
Safe git commit practices for MindRoom.
commit
智能生成 Git 提交信息并提交.
commit
Create a Conventional Commit with signoff.