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 definite-d/agent-skills --skill atomic-commitsgit clone --depth 1 https://github.com/definite-d/agent-skillsWrote 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/definite-d/agent-skills/atomic-commits)<a href="https://agentmods.dev/skills/definite-d/agent-skills/atomic-commits"><img src="https://agentmods.dev/badge/skills/definite-d/agent-skills/atomic-commits.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.1 | $0.00100 | $0.00678 |
| Opus 5 | $0.00050 | $0.00339 |
| Sonnet 5 | $0.00020 | $0.00136 |
| Haiku 4.5 | $0.00010 | $0.00068 |
Grade A, and why
atomic-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 8d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atomic Commits Skill
Transform uncommitted changes into clean, logical commits using iterative analysis.
Workflow
1. Discover
git status
git diff --stat
git diff --name-only
2. Bucket by Functionality
Group files into logical buckets:
| Bucket | Use For | Priority |
|---|---|---|
| Infrastructure | Settings, constants, base classes | 🔴 High |
| Feature/Refactor | New capability, code restructure | 🟡 Medium |
| Integration | Routes, wiring, glue code | 🟡 Medium |
| Tests | Test files | 🟢 Low |
| Build | Generated files, lock files | 🔵 Auto |
3. Order by Dependency
- Infrastructure first (others depend on it)
- Feature/Refactor (core logic)
- Integration last (wiring it together)
4. Commit Each Bucket
For cleanly separated files:
git add path/to/bucket/files
git commit -m "type(scope): description"
For mixed changes in one file: Use granular-git skill.
Commit Messages
Follow Existing Patterns First
Check git log --oneline -20 for established conventions:
- Scope names (e.g.,
backend,frontend,auth) - Type usage (e.g.,
feat,fix,refactor) - Message style
Fallback: Conventional Commits
<type>(<scope>): <description>
| Type | When |
|---|---|
feat |
New feature |
fix |
Bug fix |
refactor |
Code restructure |
chore |
Build, deps, tooling |
test |
Tests only |
style |
Formatting only |
build |
Generated files |
Description Rules
- Imperative mood: "add" not "added"
- 50 chars max
- Lowercase after scope
- No trailing period
Decision Checklist
Before each commit:
- Changes are logically related
- No unintended files
- Dependencies satisfied
- Message follows existing pattern
Merge Conflicts
When resolving, prefer the implementation that:
- Has better error handling
- Includes new features (Task, tracing)
- Follows updated patterns
See Also
What ships with it
3 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.
- 8d ago First seen · 106 lines · 100 tokens per session scan A 1464bd35ff0d
atomic-commits is a skill published in the GitHub repository definite-d/agent-skills (2 stars, last pushed 6d ago), licensed MIT. It adds 100 tokens to every session and 678 once invoked, about $0.0005 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. 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.
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…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
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…