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/adityasasidhar/claude-code-in-100-lines/git-commitnpx skills add adityasasidhar/claude-code-in-100-lines --skill git-commitgit clone --depth 1 https://github.com/adityasasidhar/claude-code-in-100-linesWrote 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/adityasasidhar/claude-code-in-100-lines/git-commit)<a href="https://agentmods.dev/skills/adityasasidhar/claude-code-in-100-lines/git-commit"><img src="https://agentmods.dev/badge/skills/adityasasidhar/claude-code-in-100-lines/git-commit.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00233 |
| Opus 5 | $0.00009 | $0.00117 |
| Sonnet 5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
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 3d 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
Use this when committing work.
Before committing
git statusandgit diff— know exactly what you are about to commit.- Do not commit unrelated changes together. One logical change per commit.
- Never commit secrets, large binaries, or debug cruft. Check for them.
The message
- Subject line: imperative mood, ~50 chars, no period. "Add retry to fetch", not "Added retries" or "fixes stuff".
- Body (when the change is not trivial): explain why, not what — the diff already shows what. Wrap at ~72 chars.
- Reference the issue/ticket if there is one.
Rules
- Commit only when the user asks.
- If on the default branch (
main/master), create a branch first. - Stage and commit, then stop. Do not
git pushunless explicitly told to. - Verify the commit landed:
git log --oneline -1.
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.
- 3d ago First seen · 25 lines · 18 tokens per session scan A 9e808d54b21f
git-commit is a skill published in the GitHub repository adityasasidhar/claude-code-in-100-lines (2 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 233 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 skills, from other repositories
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.
task-stage-report
Apply the stage completion procedure for a Hyper-Waterfall task. Write the stage report (stage{N}.md), commit stage source and report together, and run stage verification commands. Invoke after a stage completes and before entering the next stage.
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive…
commit
Commit current work with a clean, conventional message. Use when the user says "commit", "save this", "git commit", "make the commit". Do NOT use for push (that requires separate approval).
git-discipline
Git-дисциплина проекта: ветки feature/ - , Conventional Commits на русском, ритуал задачи, зелёные pytest+flake8 до коммита, секреты не коммитим.
review-before-commit
Run a behavioral self-check before persisting story results. Verifies diff simplicity, scope adherence, and verifiable completion against enso §10 behavioral principles. Use when a story's implementation is complete and ready to close.