commit

commit is a command for Claude Code from mylee04/who-ran-what. It costs 6 tokens per session (486 once invoked), scanned A, original, MIT.

A command that checks a project's shell scripts and tests before creating a Git commit, which records a set of code changes. It then reviews the changes and creates a formatted commit message.

In plain words
What is it for?
Running ShellCheck and tests, reviewing Git changes, and creating commits with standard message types.
Why use it?
It prevents committing changes when required checks fail and keeps commit messages consistent.

Command for Claude Code

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/mylee04/who-ran-what/commit
Clone the repo
git clone --depth 1 https://github.com/mylee04/who-ran-what

Made for: Claude Code.

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 commit

README.md
[![agentmods](https://agentmods.dev/badge/commands/mylee04/who-ran-what/commit.svg)](https://agentmods.dev/commands/mylee04/who-ran-what/commit)
Your own site
<a href="https://agentmods.dev/commands/mylee04/who-ran-what/commit"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/commit.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 486 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.00006 $0.00486
Opus 5 $0.00003 $0.00243
Sonnet 5 $0.00001 $0.00097
Haiku 4.5 $0.00001 $0.00049

Measured 3d ago against content hash a3e8bcb02564, 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 3d 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.

.claude/commands/commit.md · 98 lines

What it actually says

Commit Changes

What This Command Does

  1. MUST run shellcheck before committing (MANDATORY)
  2. MUST run tests before committing (MANDATORY)
  3. Reviews changes and generates commit message
  4. Creates the commit

MANDATORY Pre-Commit Checks

DO NOT COMMIT if any of these fail!

1. Shellcheck (REQUIRED)

# Run shellcheck with -x flag to follow source files
shellcheck -x bin/who-ran-what
shellcheck -x lib/who-ran-what/**/*.sh
shellcheck -x tests/*.sh

If shellcheck fails → FIX THE ISSUES FIRST, then retry commit.

2. Tests (REQUIRED)

bash tests/run_all.sh

If tests fail → FIX THE ISSUES FIRST, then retry commit.

Process (After Checks Pass)

1. Review Changes

git status
git diff --stat

2. Commit Message Format

type: brief description

- Detail 1
- Detail 2
Types
Type Use For
feat New feature
fix Bug fix
docs Documentation
refactor Code refactoring
test Adding tests
chore Maintenance

3. Example Messages

feat: add Gemini CLI parser

- Parse ~/.gemini/sessions/ for tool usage
- Support date filtering
- Match Claude parser interface
fix: handle missing session files gracefully

- Check file existence before parsing
- Log warning instead of error

Rules

  • NEVER commit without running shellcheck first
  • NEVER commit without running tests first
  • No Co-Authored-By lines
  • No .env files
  • Keep messages concise but descriptive

Quick Pre-Commit Command

Run this before every commit:

shellcheck -x bin/who-ran-what lib/who-ran-what/**/*.sh tests/*.sh && bash tests/run_all.sh && echo "✅ Ready to commit!"
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. 3d ago First seen · 98 lines · 6 tokens per session scan A a3e8bcb02564

Subscribe to this mod's changes

commit is a command published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 486 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-31.