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/adriannoes/awesome-agentic-ai/git-commitgit clone --depth 1 https://github.com/adriannoes/awesome-agentic-aiWhat 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.00328 |
| Opus 5 | $0.00000 | $0.00164 |
| Sonnet 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 2d 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.
- 2d 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 (53 stars, last pushed 4d 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
brownfield-dead
Identify all dead code in the codebase: unused files and unused exports.
onboard
Generate a personalized onboarding brief for a new developer joining the project.
brownfield-chat
Answer any structural, historical, or architectural question about the codebase without reading raw source files.
brownfield-fix
Run a risk assessment before editing any file in a brownfield codebase. Provides a risk card showing impact scope, danger zones, and safe-to-edit verdict.
brownfield-map
Run a complete brownfield analysis on the codebase and generate MASTER.md, summaries, risk scores, and all derived analytics.
brownfield-score
Detailed risk scoring breakdown for a specific file. Shows all contributing factors and project comparison.