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/virgoC0der/awesome-claude-codeWrote 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/virgoc0der/awesome-claude-code/git-commit-pusher)<a href="https://agentmods.dev/commands/virgoc0der/awesome-claude-code/git-commit-pusher"><img src="https://agentmods.dev/badge/commands/virgoc0der/awesome-claude-code/git-commit-pusher/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/virgoc0der/awesome-claude-code/git-commit-pusher"><img src="https://agentmods.dev/badge/commands/virgoc0der/awesome-claude-code/git-commit-pusher.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.00226 |
| Opus 5.5 | $0.00000 | $0.00090 |
| Sonnet 5.5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
git-commit-pusher 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.
What it actually says
Review recent code changes, generate a meaningful commit message, and push to remote.
-
Review changes:
- Run
git statusandgit diffto see what changed - Analyze whether changes are new features, bug fixes, refactoring, docs, or config
- Run
-
Generate commit message following conventional commit format:
- Use imperative mood ("Add", "Fix", "Update", "Remove")
- Keep first line under 50 characters when possible
- Use prefixes: feat:, fix:, docs:, refactor:, etc.
- Include details in the body for complex changes
-
Show what will be committed:
- Display the files to be committed
- Present the proposed commit message
- Ask for confirmation before proceeding
-
Execute git operations:
- Stage appropriate files with
git add - Create the commit
- Push to remote branch with
git push - Handle conflicts gracefully
- Stage appropriate files with
-
Report final status of the operation.
IMPORTANT: Never force push without explicit user consent. If issues occur, explain clearly and suggest solutions.
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 · 28 lines · 0 tokens per session scan A 4d0d55eae326
git-commit-pusher is a command published in the GitHub repository virgoC0der/awesome-claude-code (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 226 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
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.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.