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 OutlineDriven/odin-codex-plugin --skill atomic-commit-and-pushgit clone --depth 1 https://github.com/OutlineDriven/odin-codex-pluginWrote 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/outlinedriven/odin-codex-plugin/atomic-commit-and-push)<a href="https://agentmods.dev/skills/outlinedriven/odin-codex-plugin/atomic-commit-and-push"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/atomic-commit-and-push/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/outlinedriven/odin-codex-plugin/atomic-commit-and-push"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/atomic-commit-and-push.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.00111 | $0.00267 |
| Opus 5.5 | $0.00044 | $0.00107 |
| Sonnet 5.5 | $0.00022 | $0.00053 |
| Haiku 4.5 | $0.00011 | $0.00027 |
Grade A, and why
atomic-commit-and-push 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-commit-and-push — 100% identical, 0 lines differ
What it actually says
Atomic Commit and Push
Phase 1 — Atomic commit
Review staged + unstaged changes. Group by mechanism/file boundary. Create one commit per logical change. Run repo-native type-checker and linter before each commit. Do NOT bundle unrelated changes.
Phase 2 — Publish
Prefer git submit when git-branchless is installed and the forge is supported.
Fallback: pick a descriptive branch name, then git push origin HEAD:refs/heads/<branch>.
Set upstream only when the user explicitly wants tracking.
Never --force or --force-with-lease without explicit user authorization.
Never push directly to protected branches (e.g., main, master, release/*).
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 · 18 lines · 111 tokens per session scan A 46052a4fd02e
atomic-commit-and-push is a skill published in the GitHub repository OutlineDriven/odin-codex-plugin (14 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 111 tokens to every session and 267 once invoked, about $0.0004 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 skills, from other repositories
request-refactor-plan
Plan a refactor as a sequence of tiny, working commits via adversarial interview. Default output is a markdown plan at /docs/refactor-plans/ .md; pass --emit-issue to also file a GitHub issue. Trigger on structural refactors (rename, extract, move, split, dedupe) — NOT new features.
setup-pre-commit
Install git pre-commit hooks via the project's hook tool — Husky+lint-staged (JS), pre-commit (Python/OCaml), lefthook (Go), cargo-husky (Rust). Use when the user wants commit-time formatting, linting, type-checking, or test gates. Detects ecosystem first.
atomic-commit-and-push
Run the atomic-commit workflow on the current changes, then publish the resulting commits to the remote. Use whenever the user says "commit and push", "ship these changes", "atomic commit and push", "publish my work", or wants atomic commits delivered to origin in one step. Prefers git submit (git-branchless); falls…
atomic-commit
Review staged + unstaged changes and split them into one commit per logical change. Use whenever the user says "atomic commit", "commit my changes", "split this into commits", or has multiple unrelated edits sitting in the working tree — even if they don't say "atomic". Runs repo-native type-checker and linter before…
intuitive-squash
Safely rewrite noisy local history into reviewable commits, with aggressive or moderate plan choices, when the user explicitly asks to squash.
git-ops
Git workflow assistance for managing branches, worktrees, commits, rebases, releases, and pull or merge requests. Git is a tool for tracking code changes; a pull request or merge request proposes changes for review.