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.
git clone --depth 1 https://github.com/dinnovos/dinnovos-marketplaceWrote 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/dinnovos/dinnovos-marketplace/bro-commit-this)<a href="https://agentmods.dev/commands/dinnovos/dinnovos-marketplace/bro-commit-this"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-commit-this/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/dinnovos/dinnovos-marketplace/bro-commit-this"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-commit-this.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.00028 | $0.02767 |
| Opus 5 | $0.00014 | $0.01384 |
| Sonnet 5 | $0.00006 | $0.00553 |
| Haiku 4.5 | $0.00003 | $0.00277 |
Grade A, and why
bro-commit-this 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 8d 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Commit (Smart Multi-Commit Support)
Analyze pending files, generate descriptive messages, and execute commits. Automatically splits into multiple commits when necessary for better organization.
Step 1: Check repository status
git status --short
If there are no changes
If the command returns nothing, respond:
✅ No pending changes
Working directory is clean. Nothing to commit.
Stop here if there are no changes.
Step 2: Stage files
Check if there are staged files:
git diff --cached --name-only
If no files are staged, add all changes:
git add -A
Step 3: Analyze changes
Get the full diff of what will be committed:
git diff --cached --stat
git diff --cached
Read and analyze:
- Which files were modified/added/deleted
- What type of changes they are (feature, fix, refactor, docs, etc.)
- What is the main purpose of the change
Step 4: Smart Commit Grouping Analysis
CRITICAL STEP: Determine if changes should be split into multiple commits.
4.1 Grouping Criteria
Analyze if changes belong to DIFFERENT logical groups:
| Criterion | Split if... | Example |
|---|---|---|
| Type | Mix of feat + fix + docs | feat(auth) + fix(api) + docs(readme) |
| Scope/Module | Changes in unrelated modules | src/auth/ + src/payments/ + src/users/ |
| Purpose | Multiple independent features | New login + Bug fix in cart |
| Layer | Mix of frontend + backend + config | Components + API routes + package.json |
4.2 Grouping Decision Matrix
┌─────────────────────────────────────────────────────────────────┐
│ SHOULD I SPLIT INTO MULTIPLE COMMITS? │
├─────────────────────────────────────────────────────────────────┤
│ │
│ ✅ SINGLE COMMIT if: │
│ - All changes serve ONE purpose │
│ - All files are in the SAME module/feature │
│ - All changes are the SAME type (all feat, all fix, etc.) │
│ - Changes are interdependent (one doesn't work without other)│
│ │
│ 🔀 MULTIPLE COMMITS if: │
│ - Mix of features AND fixes │
│ - Changes to UNRELATED modules │
│ - Independent changes that happened to be made together │
│ - Documentation changes alongside code changes │
│ - Config/dependency changes alongside feature changes │
│ - Refactoring alongside new features │
│ │
└─────────────────────────────────────────────────────────────────┘
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.
- 8d ago First seen · 411 lines · 28 tokens per session scan A d2670fbdfc7d
bro-commit-this is a command published in the GitHub repository dinnovos/dinnovos-marketplace (2 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 2,767 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-31.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
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.
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.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.