commit

commit is a command for Claude Code from qqabcv520/my-claude-marketplaces. It costs 9 tokens per session (741 once invoked), scanned A, original, MIT.

A command for creating Git commits with Conventional Commits messages, a standard format such as feat or fix followed by a short description.

In plain words
What is it for?
Use it to inspect staged changes, stage all changes when needed, detect unrelated work, choose a message style, and commit the result.
Why use it?
It checks the current changes and helps create a consistent commit instead of requiring you to write the message manually.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter.

Part of the commit plugin — 1 command shipped together

Good fit Use it to inspect staged changes, stage all changes when needed, detect unrelated work, choose a message style, and commit the result.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/qqabcv520/my-claude-marketplaces/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/qqabcv520/my-claude-marketplaces

Made for: Claude Code.

Or install commit, the plugin that ships this one along with the rest of its 1 command.

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/qqabcv520/my-claude-marketplaces/commit.svg)](https://agentmods.dev/commands/qqabcv520/my-claude-marketplaces/commit)
Your own site
<a href="https://agentmods.dev/commands/qqabcv520/my-claude-marketplaces/commit"><img src="https://agentmods.dev/badge/commands/qqabcv520/my-claude-marketplaces/commit.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 741 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.00009 $0.00741
Opus 5 $0.00005 $0.00370
Sonnet 5 $0.00002 $0.00148
Haiku 4.5 $0.00001 $0.00074

Measured 7d ago against content hash 6b939ef67484, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 7d 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/commit/commands/commit.md · 104 lines

How it starts

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

Context

  • Current git status: !git status
  • Current git diff (staged and unstaged changes): !git diff HEAD
  • Current branch: !git branch --show-current
  • Recent commits: !git log --oneline -10

Your task

Based on the above context, create a git commit following Conventional Commits specification.

Command Options

  • --no-verify: Pass --no-verify flag to git commit
  • --style=simple|full:
    • simple (default): Concise single-line commit message
    • full: Detailed commit message with body and footer
  • --type=<type>: Override automatic type detection

Workflow

  1. Check staged files: Run git status to see what's staged
  2. Auto-stage if needed: If nothing is staged, run git add for all modified/new files
  3. Analyze changes: Run git diff --cached to understand staged changes
  4. Detect split need: If changes span multiple unrelated concerns, suggest splitting into atomic commits
  5. Generate commit message: Follow Conventional Commits format based on style setting
  6. Execute commit: Run git commit with the generated message

Conventional Commits Format

Simple Style (Default)

<type>[optional scope]: <description>

Example: feat(auth): add JWT token validation

Full Style

<type>[optional scope]: <description>

<body>

<footer>

Commit Types

Type When to Use
feat Adding new functionality
fix Fixing a bug
docs Documentation only changes
style Formatting, whitespace, etc
refactor Neither fixes bug nor adds feature
perf Performance improvements
test Adding or updating tests
chore Maintenance, build process, tools
ci CI/CD configuration changes
build Build system changes
revert Reverting previous commit

Rules

  • Write in present tense, imperative mood ("add" not "added")
  • Keep subject line under 72 characters
  • Capitalize first letter of description
  • No period at end of subject line
  • Use body to explain what and why (not how)
  • Pass commit message via HEREDOC for proper formatting:
    git commit -m "$(cat <<'EOF'
    type(scope): description
    
    Body text here.
    EOF
    )"
    

Read the full file on GitHub · 104 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. 7d ago First seen · 104 lines · 9 tokens per session scan A 6b939ef67484

Subscribe to this mod's changes

commit is a command published in the GitHub repository qqabcv520/my-claude-marketplaces (2 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 741 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.