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/seabbs/skillsWrote 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/agents/seabbs/skills/commit)<a href="https://agentmods.dev/agents/seabbs/skills/commit"><img src="https://agentmods.dev/badge/agents/seabbs/skills/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/agents/seabbs/skills/commit"><img src="https://agentmods.dev/badge/agents/seabbs/skills/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.00047 | $0.00493 |
| Opus 5.5 | $0.00019 | $0.00197 |
| Sonnet 5.5 | $0.00009 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
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 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
Create a well-structured commit.
Read git identity from the project's or org's CLAUDE.md ## Automation config table (bot_account, bot_email, owner_account, owner_email).
Arguments
--as-me: Commit as the owner instead of the bot account--bot-only: Commit as the bot account without co-author
Git Identity
| Mode | Git Author | Co-author |
|---|---|---|
| (default) | bot account (bot_email) | owner (owner_email) |
--as-me |
owner (owner_email) | none |
--bot-only |
bot account (bot_email) | none |
Process
-
Set git identity based on arguments:
- Default or
--bot-only:git config user.name "<bot_account>"andgit config user.email "<bot_email>" --as-me:git config user.name "<owner_account>"andgit config user.email "<owner_email>"
- Default or
-
Review and commit changes:
- Review staged and unstaged changes with
git diffandgit status - Determine commit type (feat, fix, docs, style, refactor, perf, test, build, ci, chore)
- Stage relevant files by name (exclude temp/generated: *.html, *.pdf, build/, *.log, .DS_Store)
- Write concise commit message in conventional format:
type(scope): description - Pass commit messages via a HEREDOC to preserve formatting
- Never push directly to main
- Never include "Co-Authored-By: Claude" or "Generated with Claude Code" in commit messages
- Never skip hooks (--no-verify)
- Review staged and unstaged changes with
-
Add co-author trailer (default mode only):
- Append
Co-authored-by: <owner_account> <<owner_email>>to commit message
- Append
Auto-Exit When Standalone
If this agent is being run as a standalone request, automatically exit after completing all phases successfully.
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 · 46 lines · 0 tokens per session scan A 9ce69caafbbc
commit is an agent published in the GitHub repository seabbs/skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 493 once invoked, about $0.0002 per session on Opus 5.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-08-31.
Other agents, from other repositories
git-summary
A Git commit-summary assistant that reads a code diff, meaning the changes between two versions, and writes one short description of the main change.
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
Demonstrate
Agent for demonstrating VS Code features.