agentmods.dev

atomic-git-discipline

atomic-git-discipline is a skill for Claude Code, Codex from damusix/atomic-claude. It costs 106 tokens per session (2,275 once invoked), scanned A, original, MIT.

A writing guide for concise Git commit messages and pull-request descriptions using a common format. It explains when to include the reason for a change instead of repeating what the code already shows.

In plain words
What is it for?
Use it when writing commit messages, preparing pull-request bodies, staging changes, or asking another coding agent to describe a change.
Why use it?
It removes unnecessary text while preserving important context, such as why a change was made or whether it requires a migration.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

not rated 114repo +4 changed 1mo ago A scan SkillSpector: pass 106 tokens original MIT

Good fit Use it when writing commit messages, preparing pull-request bodies, staging changes, or asking another coding agent to describe a change.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/damusix/atomic-claude/atomic-git-discipline
View source ↗ damusix/atomic-claude atomic.alonso.network
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.

Any agent
npx skills add damusix/atomic-claude --skill atomic-git-discipline
Clone the repo
git clone --depth 1 https://github.com/damusix/atomic-claude

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for atomic-git-discipline

README.md
[![agentmods](https://agentmods.dev/badge/skills/damusix/atomic-claude/atomic-git-discipline/github.svg)](https://agentmods.dev/skills/damusix/atomic-claude/atomic-git-discipline)
Your own site
<a href="https://agentmods.dev/skills/damusix/atomic-claude/atomic-git-discipline"><img src="https://agentmods.dev/badge/skills/damusix/atomic-claude/atomic-git-discipline/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.

agentmods 80×15 button for atomic-git-discipline

Your own site · 80×15
<a href="https://agentmods.dev/skills/damusix/atomic-claude/atomic-git-discipline"><img src="https://agentmods.dev/badge/skills/damusix/atomic-claude/atomic-git-discipline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,275 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00106 $0.02275
Opus 5.5 $0.00042 $0.00910
Sonnet 5.5 $0.00021 $0.00455
Haiku 4.5 $0.00011 $0.00228

Measured 1mo ago against content hash fa35f4b13a1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

atomic-git-discipline 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.

context/skills/atomic-git-discipline/SKILL.md · 171 lines

How it starts

The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.

  • "write a commit", "commit message", "generate commit"
  • "open a PR", "PR description", "PR body", writing gh pr create --body
  • Staging changes for commit
  • Ship verbs delegating message format
  • Read directly by subagents briefed to create a commit or open a PR (per CLAUDE.md Commits & PRs — subagents can't auto-fire skills)

Write commit messages terse and exact. Conventional Commits. No fluff. Why over what.

Rules

Subject line:

  • <type>(<scope>): <imperative summary> — <scope> optional
  • Types: feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert
  • Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"
  • ≤50 chars when possible, hard cap 72
  • No trailing period
  • Match project convention for capitalization after the colon

Body (only if needed):

  • Skip entirely when subject is self-explanatory
  • Add body only for: non-obvious why, breaking changes, migration notes, linked issues
  • Hard cap: 4 lines / 2 bullets. One why-sentence beats a paragraph.
  • Never restate what the diff shows — file lists, renamed symbols, mechanical changes
  • Wrap at 72 chars
  • Bullets with -, not *
  • Reference issues/PRs at end: Closes #42, Refs #17

Omit from commit messages:

  • "This commit does X", "I", "we", "now", "currently" — the diff says what
  • "As requested by..." — use Co-authored-by: trailer instead
  • "Generated with Claude Code" or any AI attribution — including Co-Authored-By: Claude trailers and session-link trailers, even when a harness suggests them
  • Emoji (unless project convention requires)
  • Restating the file name when scope already says it

Examples

  • Bad: feat: add a new endpoint to get user profile information from the database

  • Good:

    feat(api): add GET /users/:id/profile

Mobile client needs slim profile payload to cut LTE bandwidth on
cold-launch screens.

Closes #128

Read the full file on GitHub · 171 lines

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. 1mo ago Changed · +12 lines fa35f4b13a1f
  2. 1mo ago First seen · 159 lines · 106 tokens per session scan A 158e929e2955

Subscribe to this mod's changes

atomic-git-discipline is a skill published in the GitHub repository damusix/atomic-claude (114 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 2,275 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.

Claude CodeCommitsGit and workflowWriting and docsai-codinganthropicclaudeclideveloper-tools
Related

Other skills, from other repositories

setup-caliber

Sets up Caliber for automatic AI agent context sync. Installs pre-commit hooks so CLAUDE.md, Cursor rules, and Copilot instructions update automatically on every commit. Use when Caliber hooks are not yet installed or when the user asks about keeping agent configs in sync.

caliber-ai-org/ai-setup · 61 tokens

commit-pr

Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…

ZaxbyHub/opencode-swarm · 100 tokens

memstack-security-git-guard

Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…

cwinvestments/memstack · 92 tokens

git-workflow

Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…

ericrisco/rsc-harness · 127 tokens

github-workflow

GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.

Mindrally/skills · 23 tokens

git-workflow

Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.

Mindrally/skills · 23 tokens