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/virgoc0der/awesome-claude-code/git-commit-pushergit clone --depth 1 https://github.com/virgoC0der/awesome-claude-codeWhat 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.00000 | $0.00226 |
| Opus 5 | $0.00000 | $0.00113 |
| Sonnet 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 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.
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.
- yesterday 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 9mo 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.