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.
git clone --depth 1 https://github.com/spencermarx/open-code-reviewWrote 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/commands/spencermarx/open-code-review/atomic-commits)<a href="https://agentmods.dev/commands/spencermarx/open-code-review/atomic-commits"><img src="https://agentmods.dev/badge/commands/spencermarx/open-code-review/atomic-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/commands/spencermarx/open-code-review/atomic-commits"><img src="https://agentmods.dev/badge/commands/spencermarx/open-code-review/atomic-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.00014 | $0.00855 |
| Opus 5.5 | $0.00006 | $0.00342 |
| Sonnet 5.5 | $0.00003 | $0.00171 |
| Haiku 4.5 | $0.00001 | $0.00085 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- atomic-commits — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atomic Commits
Analyze staged changes along with relevant requirements and OpenSpec files, then organize and commit them as intuitive atomic commits following conventional commits.
Prerequisites
- Ensure there are staged changes (
git diff --staged) - Review any related OpenSpec change documents in
openspec/changes/
Steps
-
Analyze Staged Changes
- Run
git diff --staged --name-onlyto list all staged files - Run
git diff --stagedto understand the actual changes - Group changes by logical concern (feature, fix, refactor, docs, spec, etc.)
- Run
-
Identify Related OpenSpec Documents
- Check if any staged changes relate to OpenSpec change documents in
openspec/changes/ - If OpenSpec files are staged, note which ones are non-archived (not in
openspec/changes/archive/) - Read relevant OpenSpec documents to understand the context and requirements
- Check if any staged changes relate to OpenSpec change documents in
-
Plan Atomic Commits
- Organize changes into logical, atomic commits that each represent a single cohesive change
- Order commits in a sequence that makes sense (dependencies first, features second, cleanup last)
- OpenSpec commits: Any commit related to OpenSpec documents should use the prefix
spec: ... - Archive commit: If non-archived OpenSpec change documents are included, plan the final commit to archive them using
openspec archive <id> --yes
-
Execute Commits Sequentially
- For each atomic commit:
a. Unstage all files:
git reset HEADb. Stage only the files for this specific commit:git add <files>c. Commit with a conventional commit message:git commit -m "<type>(<scope>): <description>" - Conventional commit types:
feat,fix,refact,doc,test,chore,style,perf,ci,build,spec
- For each atomic commit:
a. Unstage all files:
-
Archive OpenSpec Changes (Final Commit)
- If OpenSpec change documents were part of the staged changes and are non-archived:
- Run
openspec archive <id> --yesfor each relevant change ID - Commit the archive with:
git commit -m "spec: archive <change-id>"
- Run
- If OpenSpec change documents were part of the staged changes and are non-archived:
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 · 80 lines · 14 tokens per session scan A 26f8353daec0
atomic-commits is a command published in the GitHub repository spencermarx/open-code-review (379 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 855 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-30.
Other commands, from other repositories
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.
replay
You are reconstructing the historical evolution of this sprint by recompiling every version of claims.json from git history.
commit
Analyze uncommitted changes, create a branch if needed, and commit with a well-structured message.
work-commit
Prepare and perform a clean commit following conventions.
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.