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 skills add jkomyno/.dotfiles --skill commit-oftengit clone --depth 1 https://github.com/jkomyno/.dotfilesWrote 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/jkomyno/.dotfiles/commit-often)<a href="https://agentmods.dev/skills/jkomyno/.dotfiles/commit-often"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/commit-often/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/jkomyno/.dotfiles/commit-often"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/commit-often.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.00036 | $0.00358 |
| Opus 5.5 | $0.00014 | $0.00143 |
| Sonnet 5.5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
commit-often 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
Commit Often
Working code that exists only in the working tree is one bad command away from gone. Commit at every logical unit so each step is small, reviewable, and individually revertible.
When to commit
- A logical unit is complete — one behavior added, one bug fixed, one rename done — and the build is green.
- Before starting anything risky: a cross-cutting refactor, a dependency bump, a migration.
- Before switching focus to a different part of the task.
If several files of churn have accumulated without a commit, stop and split out what is already complete.
How to commit
- Stage files explicitly (
git add <file> ...), nevergit add .orgit add -A. Listing files catches strays before they land. - Conventional Commits style, imperative mood:
feat:,fix:,refactor:,chore:,test:,docs:. - The message explains why; the diff already shows what.
- Never add AI attribution: no
Co-Authored-By, no "Generated with" trailers. - Don't commit broken states to "save progress". If the build is red, either finish the unit or stash.
Splitting accumulated work
When several units have piled up unstaged, don't flatten them into one
commit. Stage and commit them separately (git add -p for files that mix
units), in dependency order, each leaving the build green.
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 · 40 lines · 36 tokens per session scan A e8f6506a0f0c
commit-often is a skill published in the GitHub repository jkomyno/.dotfiles (5 stars, last pushed 17d ago), licensed MIT. It adds 36 tokens to every session and 358 once invoked, about $0.0001 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.