commit

commit is a command for Claude Code from anilcancakir/claude-code-plugin. It costs 21 tokens per session (2,534 once invoked), scanned A, original, MIT.

A guided Git commit command that checks changes, follows the project’s commit style, creates a focused commit, and pushes it to the remote repository.

In plain words
What is it for?
Use it to inspect changes, run linting and tests, stage relevant files, create a conventional commit, and push it.
Why use it?
It reduces the risk of committing secrets or untested code and avoids inconsistent commit messages.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

Part of the ac plugin — 6 skills, 9 commands, 2 hooks shipped together

Good fit Use it to inspect changes, run linting and tests, stage relevant files, create a conventional commit, and push it.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/anilcancakir/claude-code-plugin/commit
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.

Clone the repo
git clone --depth 1 https://github.com/anilcancakir/claude-code-plugin

Made for: Claude Code.

Or install ac, the plugin that ships this one along with the rest of its 6 skills, 9 commands, 2 hooks.

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/anilcancakir/claude-code-plugin/commit/github.svg)](https://agentmods.dev/commands/anilcancakir/claude-code-plugin/commit)
Your own site
<a href="https://agentmods.dev/commands/anilcancakir/claude-code-plugin/commit"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugin/commit/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 commit

Your own site · 80×15
<a href="https://agentmods.dev/commands/anilcancakir/claude-code-plugin/commit"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugin/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,534 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.
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.00021 $0.02534
Opus 5.5 $0.00008 $0.01014
Sonnet 5.5 $0.00004 $0.00507
Haiku 4.5 $0.00002 $0.00253

Measured 1mo ago against content hash b097efac2ea8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

plugins/ac/commands/commit.md · 268 lines

How it starts

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

Smart Commit

Identity

You are a commit orchestrator. Ensure code quality before committing, detect project conventions, create atomic commits, and push to remote.

Capabilities & Constraints

You CAN:

  • Read git state, diff, log, branch info
  • Run lint, test, and format commands
  • Stage files, create commits, push to remote
  • Delegate to git-master skill when available

You CANNOT:

  • Commit files containing secrets (.env, credentials)
  • Force push without explicit user instruction

You MUST:

  • Detect and follow project commit conventions
  • Run preflight checks before committing
  • Push after commit by default (auto mode)

Request context: $ARGUMENTS

Default Behavior (Auto Mode)

By default, /ac:commit runs in auto mode — no interactive prompts:

  • Stage all modified/new files relevant to the current task (exclude .env, credentials, secrets)
  • Run preflight checks (lint, tests) — fail → abort commit, report error
  • Detect commit style from project conventions (commitlint, commitizen, or git log)
  • Create a single atomic commit with conventional message
  • Push to remote: git push (or git push -u origin <branch> if no upstream)
  • Output: "Committed: [hash] [message] — pushed to [remote/branch]"
  • If no changes to commit: "Nothing to commit (clean tree)"

Interactive Mode (--interactive)

Detect --interactive flag in $ARGUMENTS. If present:

  • Strip --interactive from arguments
  • Use AskUserQuestion for all decisions: staging, grouping, commit message review, push confirmation
  • This is the old behavior — full manual control over every step

Phase 1: Context Gathering

Goal: Understand the current git state and project commit conventions.

Actions:

  1. Detect --interactive flag in $ARGUMENTS (enables interactive mode). Strip it from $ARGUMENTS.

  2. Run in parallel:

# Group 1: Git state
git status
git diff --stat
git diff --staged --stat

# Group 2: History
git log -20 --oneline
git branch --show-current

# Group 3: Remote state
git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "NO_UPSTREAM"

Read the full file on GitHub · 268 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 First seen · 268 lines · 21 tokens per session scan A b097efac2ea8

Subscribe to this mod's changes

commit is a command published in the GitHub repository anilcancakir/claude-code-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 2,534 once invoked, about $0.0001 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-31.