commit

A command that checks staged Git changes and creates a commit from them.

In plain words
What is it for?
Use it to review the staged diff, check shared-work rules, commit a specific set of files, and record the commit in the coordination board when one exists.
Why use it?
It catches whitespace errors, conflict markers, outdated project notes, and coordination problems before changes are committed.

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/fockus/skill-memory-bank/commit
Clone the repo
git clone --depth 1 https://github.com/fockus/skill-memory-bank
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 713 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.00007 $0.00713
Opus 5 $0.00003 $0.00357
Sonnet 5 $0.00001 $0.00143
Haiku 4.5 $0.00001 $0.00071

Measured 2d ago against content hash 909757cb1b1d, 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.

commands/commit.md · 89 lines

How it starts

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

0. Pre-flight safety checks

# Memory Bank drift — if the bank exists
[ -d .memory-bank ] && bash ~/.claude/skills/memory-bank/scripts/mb-drift.sh .

# Conflict markers / whitespace errors in what is about to be committed
git diff --check --cached
git diff --check

# Cross-session coordination board — if parallel sessions share this tree
[ -f .memory-bank/COORDINATION.md ] && tail -40 .memory-bank/COORDINATION.md

If drift_warnings > 0, show the warnings to the user and ask whether to proceed. If git diff --check finds conflict markers or trailing-whitespace errors, stop and surface them — do not commit broken content.

If the coordination board exists, read its recent entries before committing: verify no FREEZE covers your files and the agreed commit ordering allows you to commit now; stage a scoped file list (never git add -A — the tree contains the other session's uncommitted diff), and append a COMMIT entry (hash + file scope) to the board after committing. Protocol: references/coordination.md.

1. Show staged changes

git status --short
git diff --cached --stat
git diff --cached

2. Scan the staged diff for forbidden patterns

Check for (in added lines only):

  • Debug residue: fmt.Println, console.log, debugger;, print( (language-appropriate)
  • TODO / FIXME / HACK markers in new code
  • Commented-out code blocks
  • Hardcoded secrets (use the grep shape from /security-review)
  • Files that should not be committed: .env, *.pem, *.key, credentials.json

If any match appears, show the findings and ask whether to continue.

3. Draft the commit message

Conventional Commits format: <type>(<scope>): <subject>

  • Types: feat, fix, refactor, test, docs, chore, perf, build, ci, style
  • Scope: optional, derive from most-changed top-level directory when non-trivial
  • Subject: imperative, ≤72 chars, no trailing period

If $ARGUMENTS is provided, use it as the subject (or the full message, if it looks complete). Otherwise synthesize from the staged diff.

Read the full file on GitHub · 89 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. 2d ago First seen · 89 lines · 7 tokens per session scan A 909757cb1b1d

Subscribe to this mod's changes

commit is a command published in the GitHub repository fockus/skill-memory-bank (25 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 713 once invoked, about $0.0000 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.