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 skills/paulrberg/agent-skills/commitnpx skills add PaulRBerg/agent-skills --skill commitgit clone --depth 1 https://github.com/PaulRBerg/agent-skillsWhat 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.00041 | $0.01827 |
| Opus 5 | $0.00020 | $0.00914 |
| Sonnet 5 | $0.00008 | $0.00365 |
| Haiku 4.5 | $0.00004 | $0.00183 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Compose the semantic commit message from immutable evidence. Let ai-commit own deterministic preparation, commit,
index reconciliation, and push mechanics.
Run every command from the target repository cwd. Do not surround ai-commit with extra git status, git log, or
git diff calls: preparation provides the complete evidence for this workflow. Use --porcelain only in deterministic
automation that explicitly parses its stable TSV records; the normal skill flow consumes the human-readable sections.
1. Parse Arguments
Arguments: $ARGUMENTS
ai-commitselects the message format from repository config; pass--naturalor--conventionalonly as an explicit one-off override, never to reproduce repository policy.--all: capture all worktree and index changes. This intentionally risks including another agent's work.--staged: capture exactly the current index; do not add session paths. It conflicts with--all.--natural: force Natural Language Format for this commit.--conventional: force Conventional Prefix Format for this commit.--push: request a push after commit. Otherwise push only when standing instructions authorize it.--close <issue_numbers>: append oneCloses #Ntrailer per positive decimal issue number; accept comma- or space-separated input.--finding <finding_ids>: append oneFinding-ID: <id>trailer per ledger finding this commit fixes; accept comma- or space-separated input. Also infer a finding from context when this session's commit fixes a specific ledger finding. Never include or resolve findings the commit does not actually fix.- In Conventional Prefix Format, a positional type keyword overrides the inferred type. In Natural Language Format, a positional verb or category keyword overrides the inferred verb. Quoted positional text overrides the inferred description or subject.
If the requested operation is only to push a clean branch that is already ahead, skip preparation and run
ai-commit push.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 138 lines · 41 tokens per session scan A 07a16292dde4
commit is a skill published in the GitHub repository PaulRBerg/agent-skills (70 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 1,827 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-08-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
keploy-pr-workflow
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…