Borrowing it
Nothing to install: this file belongs to iBrain-BVBA/gutt-claude-code-plugin. 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/iBrain-BVBA/gutt-claude-code-plugin/main/.claude/commands/commit-push-pr.mdgit clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-pluginWrote 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/ibrain-bvba/gutt-claude-code-plugin/commit-push-pr)<a href="https://agentmods.dev/commands/ibrain-bvba/gutt-claude-code-plugin/commit-push-pr"><img src="https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/commit-push-pr/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/ibrain-bvba/gutt-claude-code-plugin/commit-push-pr"><img src="https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/commit-push-pr.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.00000 | $0.00713 |
| Opus 5.5 | $0.00000 | $0.00285 |
| Sonnet 5.5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit, Push, and PR Command
/commit-push-pr - Commit changes, push to remote, and create a pull request.
Usage
/commit-push-pr [PROJ-XXX] # With ticket reference
/commit-push-pr # Will prompt for details
/commit-push-pr --draft # Create as draft PR
Workflow
Step 1: Check Memory for Commit Standards
search_memory_nodes(query="commit message format git workflow", entity="WorkingAgreement", max_nodes=5)
Step 2: Stage Changes
git status
git add -A # Or selective staging
Step 3: Create Commit Message
Format: type(scope): PROJ-XXX message
| Type | Use When |
|---|---|
feat |
New feature |
fix |
Bug fix |
refactor |
Code restructure, no behavior change |
docs |
Documentation only |
test |
Adding/fixing tests |
chore |
Maintenance, deps, config |
style |
Formatting, no code change |
Examples:
feat(auth): PROJ-123 Add OAuth2 token refresh
fix(api): PROJ-456 Handle null response in user endpoint
refactor(db): PROJ-789 Extract connection pooling logic
Step 4: Commit and Push
git commit -m "type(scope): PROJ-XXX message"
git push -u origin [branch-name]
Step 5: Create Pull Request
create_pull_request(
owner="[owner]",
repo="[repo]",
title="type(scope): PROJ-XXX Brief description",
body="""
## Summary
[What this PR does]
## Ticket
[PROJ-XXX](https://your-tracker.example.com/browse/PROJ-XXX)
## Changes
- [Change 1]
- [Change 2]
## Testing
- [ ] Unit tests pass
- [ ] Manual testing done
## Screenshots (if UI)
[Add screenshots]
""",
head="[branch-name]",
base="main",
draft=False
)
Step 6: Link PR to Ticket (Optional)
If using Jira integration, add a comment to the ticket with the PR link:
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.
- 1mo ago First seen · 132 lines · 0 tokens per session scan A 86f6ca78b13f
commit-push-pr is a command published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 713 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-08-31.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
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.
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.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.