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 skills add bengous/claude-code-plugins --skill commitgit clone --depth 1 https://github.com/bengous/claude-code-pluginsWrote 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/skills/bengous/claude-code-plugins/commit)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/commit"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/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/skills/bengous/claude-code-plugins/commit"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/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.00049 | $0.00456 |
| Opus 5 | $0.00024 | $0.00228 |
| Sonnet 5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
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 today.
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
Commit
Context
- Status: !
git status --short - Diff, staged and unstaged: !
git diff HEAD - Branch: !
git branch --show-current - Recent commits: !
git log --oneline -10
Task
- Scope. Something staged: commit that, leave the rest alone. Nothing staged: stage what forms one commit from the diff above, leave the rest. The diff omits untracked files; they appear as
??in the status, and a new file that the diff's changes import belongs to the same commit. A file that carries a secret is never staged, whatever the diff shows:.envand its variants, a private key, a credentials or token file. Name it and stop. - Issue. A number in
$ARGUMENTS, else the leading number of the branch name (fix/123-popoveris 123).--no-close, or no number in either place: no trailer, and no question. Otherwise the last line of the body isCloses #<n>. - Message. Follow the convention visible in the recent commits above. Subject in the imperative, no trailing period. The body says why, never what the diff shows.
- One batch. Stage and commit in a single tool batch, with nothing in between.
- Report. The happy path says nothing beyond the commit. One line, when it applies: a file left unstaged on purpose, or a
Closestrailer on a branch that is not the default, since GitHub closes the issue only when the commit reaches that default branch.
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.
- today First seen · 24 lines · 49 tokens per session scan A 39853e4dde17
commit is a skill published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 456 once invoked, about $0.0002 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-09-11.
Other skills, from other repositories
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.
ag-rebobinar
Undo estruturado. Reverte N acoes do Claude com log detalhado do que foi desfeito. Vai alem de git checkout — rastreia mudancas por sessao, arquivo, e commit, com opcao de revert seletivo.
ag-versionar-codigo
Gerencia git - branches, commits semanticos, PRs, releases e changelog. Use ao final de cada fase ou feature para manter historico limpo.