agentmods.dev

commit

A command that prepares Git commits with conventional commit messages and emoji, after checking the project and reviewing the changes.

In plain words
What is it for?
Use it to stage modified files, run pre-commit checks, determine the change type, create a commit, and push it.
Why use it?
It reduces the manual work of staging files, checking pre-commit validation, understanding the diff, and writing a consistent commit message. It also specifies that commits should be pushed.

Command

43 2mo ago A scan 11 tokens original MIT
View the source file jjmartres/ai-coding-agents
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/jjmartres/ai-coding-agents/commit
Clone the repo
git clone --depth 1 https://github.com/jjmartres/ai-coding-agents
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,873 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.00011 $0.01873
Opus 5 $0.00005 $0.00937
Sonnet 5 $0.00002 $0.00375
Haiku 4.5 $0.00001 $0.00187

Measured yesterday against content hash 0e954c4ba42d, 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 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.

shared/.ai-agents/commands/commit.md · 159 lines

How it starts

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

Commit Command

You are an AI agent that helps create well-formatted git commits with conventional commit messages and emoji icons, follow these instructions exactly. Always run and push the commit, you don't need to ask for confirmation unless there is a big issue or error.

Prefer to explain WHY something was done from an end user perspective instead of WHAT was done.

Instructions for Agent

When the user runs this command, execute the following workflow:

  1. Check command mode:
    • If user you have $ARGUMENTS which is simple, skip to step 3
  2. Run pre-commit validation:
    • Execute pre-commit run -a and report any issues
    • If fails, ask user if they want to proceed anyway or fix issues first
  3. Analyze git status:
    • Run git status --porcelain to check for changes
    • If no files are staged, run git add . to stage all modified files
    • If files are already staged, proceed with only those files
  4. Analyze the changes:
    • Run git diff --cached to see what will be committed
    • Analyze the diff to determine the primary change type (feat, fix, docs, etc.)
    • Identify the main scope and purpose of the changes
  5. Generate commit message:
    • Choose appropriate emoji and type from the reference below
    • Create message following format: <emoji> <type>: <description>
    • Keep description concise, clear, and in imperative mood
    • Show the proposed message to user for confirmation
  6. Execute the commit:
    • Run git commit -m "<generated message>"
    • Display the commit hash and confirm success
    • Provide brief summary of what was committed

Commit Message Guidelines

When generating commit messages, follow these rules:

  • Atomic commits: Each commit should contain related changes that serve a single purpose
  • Imperative mood: Write as commands (e.g., "add feature" not "added feature")
  • Concise first line: Keep under 72 characters
  • Conventional format: Use <emoji> <type>: <description> where type is one of:
    • feat: A new feature
    • fix: A bug fix
    • docs: Documentation changes
    • style: Code style changes (formatting, etc.)
    • refactor: Code changes that neither fix bugs nor add features
    • perf: Performance improvements
    • test: Adding or fixing tests
    • chore: Changes to the build process, tools, etc.
  • Present tense, imperative mood: Write commit messages as commands (e.g., "add feature" not "added feature")
  • Concise first line: Keep the first line under 72 characters
  • Emoji: Each commit type is paired with an appropriate emoji:
    • ✨ feat: New feature
    • 🐛 fix: Bug fix
    • 📝 docs: Documentation
    • 💄 style: Formatting/style
    • ♻️ refactor: Code refactoring
    • ⚡️ perf: Performance improvements
    • ✅ test: Tests
    • 🔧 chore: Tooling, configuration
    • 🚀 ci: CI/CD improvements
    • 🗑️ revert: Reverting changes
    • 🧪 test: Add a failing test
    • 🚨 fix: Fix compiler/linter warnings
    • 🔒️ fix: Fix security issues
    • 👥 chore: Add or update contributors
    • 🚚 refactor: Move or rename resources
    • 🏗️ refactor: Make architectural changes
    • 🔀 chore: Merge branches
    • 📦️ chore: Add or update compiled files or packages
    • ➕ chore: Add a dependency
    • ➖ chore: Remove a dependency
    • 🌱 chore: Add or update seed files
    • 🧑‍💻 chore: Improve developer experience
    • 🧵 feat: Add or update code related to multithreading or concurrency
    • 🔍️ feat: Improve SEO
    • 🏷️ feat: Add or update types
    • 💬 feat: Add or update text and literals
    • 🌐 feat: Internationalization and localization
    • 👔 feat: Add or update business logic
    • 📱 feat: Work on responsive design
    • 🚸 feat: Improve user experience / usability
    • 🩹 fix: Simple fix for a non-critical issue
    • 🥅 fix: Catch errors
    • 👽️ fix: Update code due to external API changes
    • 🔥 fix: Remove code or files
    • 🎨 style: Improve structure/format of the code
    • 🚑️ fix: Critical hotfix
    • 🎉 chore: Begin a project
    • 🔖 chore: Release/Version tags
    • 🚧 wip: Work in progress
    • 💚 fix: Fix CI build
    • 📌 chore: Pin dependencies to specific versions
    • 👷 ci: Add or update CI build system
    • 📈 feat: Add or update analytics or tracking code
    • ✏️ fix: Fix typos
    • ⏪️ revert: Revert changes
    • 📄 chore: Add or update license
    • 💥 feat: Introduce breaking changes
    • 🍱 assets: Add or update assets
    • ♿️ feat: Improve accessibility
    • 💡 docs: Add or update comments in source code
    • 🗃️ db: Perform database related changes
    • 🔊 feat: Add or update logs
    • 🔇 fix: Remove logs
    • 🤡 test: Mock things
    • 🥚 feat: Add or update an easter egg
    • 🙈 chore: Add or update .gitignore file
    • 📸 test: Add or update snapshots
    • ⚗️ experiment: Perform experiments
    • 🚩 feat: Add, update, or remove feature flags
    • 💫 ui: Add or update animations and transitions
    • ⚰️ refactor: Remove dead code
    • 🦺 feat: Add or update code related to validation
    • ✈️ feat: Improve offline support

Read the full file on GitHub · 159 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 · 159 lines · 11 tokens per session scan A 0e954c4ba42d

Subscribe to this mod's changes

commit is a command published in the GitHub repository jjmartres/ai-coding-agents (43 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 1,873 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-08-30.

Git and workflowagentsagentskillsclaude-codeclaude-skillsconfigurationdotfiles
Related

Other commands, from other repositories

publish

Release a new package version — semver bump from commits, tag, registry publish, GitHub Release.

OzzyCzech/dotfiles · 20 tokens

rebase

Rebase the current branch on main, a local branch, or a remote branch (with fetch).

OzzyCzech/dotfiles · 20 tokens

python-review

Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.

Cyvid7-Darus10/claude-code-config · 31 tokens

test-coverage

Analyze test coverage, identify gaps, and generate missing tests to reach 80%+ coverage.

Cyvid7-Darus10/claude-code-config · 0 tokens

release

Bump version, update CHANGELOG.md, and prepare a release.

yelmuratoff/agent_sync · 13 tokens

fix-issue

Investigate and fix a GitHub issue.

yelmuratoff/agent_sync · 8 tokens