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/adriannoes/awesome-agentic-aiWrote 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/adriannoes/awesome-agentic-ai/git-commit)<a href="https://agentmods.dev/commands/adriannoes/awesome-agentic-ai/git-commit"><img src="https://agentmods.dev/badge/commands/adriannoes/awesome-agentic-ai/git-commit/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/adriannoes/awesome-agentic-ai/git-commit"><img src="https://agentmods.dev/badge/commands/adriannoes/awesome-agentic-ai/git-commit.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.00328 |
| Opus 5.5 | $0.00000 | $0.00131 |
| Sonnet 5.5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
git-commit 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
Git Commit
Overview
Create a git commit for the current changes using Conventional Commits-style format.
Source: mitsuhiko/agent-stuff (Apache-2.0)
Format
<type>(<scope>): <summary>
- type (required):
featfor new features,fixfor bug fixes. Other common types:docs,refactor,chore,test,perf. - scope (optional): Short noun in parentheses for the affected area (e.g.,
api,parser,ui). - summary (required): Short, imperative, ≤ 72 chars, no trailing period.
Rules
- Body is optional. If needed, add a blank line after the subject and write short paragraphs.
- Do NOT include breaking-change markers or footers.
- Do NOT add sign-offs.
- Only commit; do NOT push unless explicitly requested.
- If unclear whether a file should be included, ask the user which files to commit.
Steps
- Review
git statusandgit diffto understand current changes - (Optional) Run
git log -n 50 --pretty=format:%sto see commonly used scopes - If ambiguous extra files exist, ask the user for clarification before committing
- Stage only the intended files
- Run
git commit -m "<type>(<scope>): <summary>"(and-m "<body>"if needed)
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 · 32 lines · 0 tokens per session scan A b444583ba14b
git-commit is a command published in the GitHub repository adriannoes/awesome-agentic-ai (68 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 328 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-30.
Other commands, from other repositories
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
summarize-changes
Summarize recent changes for standup, PR, or documentation.
pr-reviewer
Review a Git branch as a PR against the base branch (auto-resolved — main/master) judged by THIS repo's contract (CLAUDE.md + .claude/skills/). Three-dot diff, route changed paths to skills, verify (eslint/prettier/tsc + tests), tiered report + confidence. Optional gated fix + commit after the report.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
branch-commit
Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…