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/robconery/cassini-workshop/git-commitgit clone --depth 1 https://github.com/robconery/cassini-workshopWhat 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.00024 | $0.00925 |
| Opus 5 | $0.00012 | $0.00463 |
| Sonnet 5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
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 yesterday.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- git-commit — 100% identical, 0 lines differ
- git-commit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commit
Create a clean, well-described commit for the current working changes.
Defers to the github skill for branching and message format.
Behavior
- Inspect first. Run in parallel:
git status(no-uall)git diff(staged + unstaged)git log -n 10 --onelineto match the project's commit stylels .gitignoreto confirm a.gitignoreexists
- Require a
.gitignore. If one is missing, stop and offer to create one scaffolded to the project (Bun/Node/TS by default —node_modules/,dist/,.env*,.DS_Store, IDE folders, build artifacts). Do not proceed with the commit until the user accepts or provides their own. If.gitignoreexists, glance at it and warn if anything obviously sensitive in the diff isn't covered. - Check change size first. Roughly: count files changed and lines
touched. If it looks like a lot (rule of thumb: >10 files OR
300 lines OR touches >2 distinct concerns), stop and ask whether a short-lived branch would be better. Recommend a name in
<type>/<slug>form derived from the diff (e.g.feat/order-fulfillment-tx). Wait for the user before continuing. - Decide branch vs trunk per
githubskill:- Trunk → commit straight to
mainfor tiny, obvious changes. - Branch → create
<type>/<short-slug>if the change is non-trivial, spans multiple files meaningfully, or implements a story task.
- Trunk → commit straight to
- Stage everything with
-am. Usegit commit -am "<summary>"(with-Ffor the long body via a HEREDOC file when needed) so tracked modifications and deletions are all included — nothing gets left behind. For brand-new untracked files,git add <file>them explicitly first (since-awon't pick those up). Always re-scan for likely secrets (.env*,*.pem,*credentials*, API tokens in the diff) before staging — refuse the commit if any are found, name the file, and ask the user. - Write the message per the
githubskill:- Conventional Commit summary (
<type>(<scope>): <imperative>). - Detailed body: what changed, why, trade-offs. Wrap ~72 cols.
- Footers:
Refs <story-id>/Closes #<n>where applicable.
- Conventional Commit summary (
- Commit via HEREDOC so formatting is preserved. Append:
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> - Verify with
git statusafter the commit. If a hook fails, fix the underlying issue and create a NEW commit — never--amendwithout being asked.
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.
- yesterday First seen · 74 lines · 24 tokens per session scan A 8072a7d74274
git-commit is a command published in the GitHub repository robconery/cassini-workshop (1 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 925 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git-remote
Create the GitHub remote for this project and make it look sharp — name, license, real README, contributing, security, issue templates.
git-merge
Merge the current branch into main safely — commit-check, remote sync, confirm, merge.
git-commit
Stage and commit current changes using Conventional Commits, branch-or-trunk by size. Uses the github skill.
init
Scaffold the project files I like — CLAUDE.md and the /docs skeleton.
git-pr
Open a pull request with a clear summary, verification plan, and risk note via gh pr create. Uses the github skill.
git-issue
Open a GitHub issue with a clear, detailed body via gh issue create. Uses the github skill.