commit

A command that stages changes, creates a Git commit, and can optionally continue by pushing the branch, opening a pull request, merging, or squashing commits. Git is a tool for tracking code changes, and a pull request is a proposed change for review.

In plain words
What is it for?
Use it to save completed work in Git and optionally publish it, request review, merge it into the base branch, or combine its commits.
Why use it?
It combines the usual steps after coding into one controlled workflow. Without an explicit shipping choice, it commits first and asks how far to continue.

Command

Install

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.

agentmods
npx agentmods add commands/damusix/atomic-claude/commit
Clone the repo
git clone --depth 1 https://github.com/damusix/atomic-claude
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 552 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00055 $0.00552
Opus 5 $0.00028 $0.00276
Sonnet 5 $0.00011 $0.00110
Haiku 4.5 $0.00006 $0.00055

Measured 2d ago against content hash c50832aa0378, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commit 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 2d 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.

context/commands/commit.md · 73 lines

What it actually says

Parse arguments

Read $ARGUMENTS. Scan for escalation tokens: push, pr, merge, squash, squash merge.

Token → escalation mapping:

Token(s) in args Path
(none) commit only, then ask
push commit + push
pr commit + push + PR
merge commit + merge to base
squash (without merge) commit + squash branch
squash merge (both tokens) commit + squash + merge to base

If the args contain none of the tokens above, run the commit step, then prompt (see "Interactive path" below).

Commit

{{ template "commit-flow" . }}

If nothing to commit and branch has commits ahead of base, skip to the escalation step. If nothing to commit and branch is up to date with base, stop.

Escalation

Push path (push token or user picks Push)

{{ template "push-flow" . }}

PR path (pr token or user picks Open PR)

{{ template "push-flow" . }}

{{ template "pr-flow" . }}

Merge path (merge token or user picks Merge to base)

{{ template "merge-flow" . }}

Squash path (squash token, no merge, or user picks Squash branch)

{{ template "squash-flow" . }}

Squash + merge path (squash merge tokens or user picks Squash + merge)

{{ template "squash-flow" . }}

{{ template "merge-flow" . }}

Interactive path

If no escalation token was present in args, after the commit completes, ask via AskUserQuestion:

Committed. Ship further?

  • Done — just the commit
  • Push to remote
  • Open PR
  • Merge to base
  • Squash + merge

Route the answer to the matching escalation path above. "Done" stops immediately.

{{ template "git-safety" . }}

Changes

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.

  1. 2d ago First seen · 73 lines · 55 tokens per session scan A c50832aa0378

Subscribe to this mod's changes

commit is a command published in the GitHub repository damusix/atomic-claude (83 stars, last pushed 8d ago), licensed MIT. It adds 55 tokens to every session and 552 once invoked, about $0.0003 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-30.