Borrowing it
Nothing to install: this file belongs to opensesh/karimo-overview. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensesh/karimo-overview/main/.claude/skills/incremental-commits/SKILL.mdgit clone --depth 1 https://github.com/opensesh/karimo-overviewWrote 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/opensesh/karimo-overview/incremental-commits)<a href="https://agentmods.dev/skills/opensesh/karimo-overview/incremental-commits"><img src="https://agentmods.dev/badge/skills/opensesh/karimo-overview/incremental-commits/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/opensesh/karimo-overview/incremental-commits"><img src="https://agentmods.dev/badge/skills/opensesh/karimo-overview/incremental-commits.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.00000 | $0.01229 |
| Opus 5 | $0.00000 | $0.00615 |
| Sonnet 5 | $0.00000 | $0.00246 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
incremental-commits 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 5d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incremental Commits
This skill activates during plan execution, multi-phase work, or TodoWrite usage. Triggers on phrases like "plan", "phase", "task", "implement", "execute", "execute the plan", "work through", "complete the tasks".
The Iron Law
COMMIT AFTER EACH LOGICAL UNIT OF WORK — SUMMARIZE AT END
Never bundle. Never ask at the end. Commit as you go. Bundling all changes into one commit destroys traceability and makes git history useless for debugging, reverting, or understanding why changes were made.
Commit Triggers
Execute a commit when ANY of these occur:
| Trigger | Action |
|---|---|
TodoWrite task marked completed |
Commit that task's changes |
| Plan phase complete | Commit phase changes |
| Bug fix verified | Commit the fix |
| Refactor complete | Commit separately from features |
| Before context switch | Commit current work first |
The Commit Sequence
Before marking a TodoWrite task as completed:
1. VERIFY → Tests pass, build succeeds (via verification-before-completion)
2. STAGE → Stage files related to this task only
3. COMMIT → Use conventional commit format
4. MARK → Update TodoWrite status to completed
5. NEXT → Move to next task
Skipping steps = poor git history = future pain
Integration Points
With TodoWrite
When marking a task completed, commit FIRST:
❌ WRONG:
[mark TodoWrite task completed]
[continue to next task]
...later...
"Should I commit all these changes?"
✅ CORRECT:
[complete task work]
[verify it works]
[git add relevant files]
[git commit -m "feat(feature): add component skeleton"]
[mark TodoWrite task completed]
[move to next task]
With verification-before-completion
Always verify BEFORE committing:
[implement feature]
↓
[run tests - they pass]
↓
[run build - it succeeds]
↓
[commit with confidence]
What ships with it
1 file 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.
- 5d ago First seen · 204 lines · 0 tokens per session scan A 905b3ae4159b
incremental-commits is a skill published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,229 tokens. 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-03.
Other skills, from other repositories
attribution
Commit authorship policy — no co-author trailers, user is sole author.
git
This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", "manage branches", "fix merge conflicts", "undo a commit", "comment on a PR", "create a release", or performs any git/GitHub operations. Provides safety patterns, atomic commit formatting, PR descriptions…
git-github
Git workflow and GitHub collaboration patterns including conventional commits, branch naming, PR workflow, and gh CLI usage. Use when creating commits, branches, or pull requests. TRIGGER when: git commit, branch, PR, pull request, merge, gh cli. DO NOT TRIGGER when: code implementation, testing, documentation without…
brain-github-export
Export accumulated brain knowledge as CONVENTIONS.md and open a GitHub PR so your whole team can review what the AI team learned.
ship
Alles abschliessen — commit, push, PR, merge, zurück auf main. Vollständig autonom, NULL Rückfragen. Unterstützt /ship T-{N} für direkten Branch-Zugriff.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…