smart-commit

smart-commit is a command for coding agents from armanzeroeight/fastagent-plugins. It costs 14 tokens per session (794 once invoked), scanned A, original, MIT.

A command that examines staged Git changes, creates a conventional commit message, and makes the commit.

In plain words
What is it for?
Use it to create commits for features, fixes, documentation, tests, refactoring, or maintenance, with an option to amend the previous commit.
Why use it?
It removes the repetitive work of summarizing staged changes and applying the team’s commit-message format.

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/armanzeroeight/fastagent-plugins/smart-commit
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins

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 smart-commit

README.md
[![agentmods](https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/smart-commit.svg)](https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/smart-commit)
Your own site
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/smart-commit"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/smart-commit.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 794 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.00014 $0.00794
Opus 5 $0.00007 $0.00397
Sonnet 5 $0.00003 $0.00159
Haiku 4.5 $0.00001 $0.00079

Measured yesterday against content hash a7ab02bfede5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

smart-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 yesterday.

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/git-workflow-toolkit/commands/smart-commit.md · 132 lines

How it starts

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

Smart Commit

Context

  • Current branch: !git branch --show-current
  • Staged changes: !git diff --staged --stat
  • Recent commits: !git log --oneline -3

Your Task

Analyze staged changes and generate a conventional commit message, then create the commit.

Arguments

  • --amend (optional): Amend the last commit instead of creating new one
  • --no-verify (optional): Skip pre-commit hooks

Steps

  1. Analyze staged changes:

    git diff --staged
    
  2. Determine commit type based on changes:

    • feat: New feature or functionality
    • fix: Bug fix
    • docs: Documentation only
    • style: Formatting, whitespace
    • refactor: Code restructuring
    • test: Adding or updating tests
    • chore: Maintenance, dependencies
    • perf: Performance improvement
  3. Identify scope (optional):

    • Component name (e.g., auth, api, ui)
    • Module name (e.g., payments, users)
    • Feature area (e.g., dashboard, settings)
  4. Generate commit message following format:

    <type>(<scope>): <description>
    
    [optional body]
    
    [optional footer]
    
  5. Create commit:

    git commit -m "type(scope): description"
    

    Or for detailed message:

    git commit -m "type(scope): description" -m "Body text" -m "Footer text"
    
  6. Confirm commit:

    git log -1 --pretty=format:"%h - %s"
    

Examples

Simple feature commit:

/smart-commit
# Analyzes: Added new login form component
# Generates: feat(auth): add login form component
# Commits with generated message

Bug fix with details:

/smart-commit
# Analyzes: Fixed null pointer in user service
# Generates:
# fix(users): handle null response in getUserById
#
# Previously crashed when user data was null.
# Now returns 404 with appropriate error message.
#
# Fixes #123

Amend last commit:

/smart-commit --amend
# Updates the last commit message based on current staged changes

Read the full file on GitHub · 132 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. yesterday First seen · 132 lines · 14 tokens per session scan A a7ab02bfede5

Subscribe to this mod's changes

smart-commit is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 794 once invoked, about $0.0001 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-09-03.