commit

commit is a command for coding agents from sampleXbro/agentsmesh. It costs 8 tokens per session (229 once invoked), scanned A, original, MIT.

A command that reviews current Git changes and creates a commit message following a shared format. A commit is a saved set of changes in Git, and the conventional format labels its purpose, such as a feature or fix.

In plain words
What is it for?
Use it to inspect staged and unstaged changes, propose a conventional commit message, stage relevant files when appropriate, and create the commit.
Why use it?
It helps turn an uncommitted diff into a clear, consistent project record. It also prompts review of what changed before the work is saved.

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/samplexbro/agentsmesh/commit
Clone the repo
git clone --depth 1 https://github.com/sampleXbro/agentsmesh

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/samplexbro/agentsmesh/commit.svg)](https://agentmods.dev/commands/samplexbro/agentsmesh/commit)
Your own site
<a href="https://agentmods.dev/commands/samplexbro/agentsmesh/commit"><img src="https://agentmods.dev/badge/commands/samplexbro/agentsmesh/commit.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 229 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.00008 $0.00229
Opus 5 $0.00004 $0.00114
Sonnet 5 $0.00002 $0.00046
Haiku 4.5 $0.00001 $0.00023

Measured yesterday against content hash 3e6dcc5871ad, 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.

.agentsmesh/commands/commit.md · 22 lines

What it actually says

Review the current git changes (staged and unstaged) and:

  1. Analyze changes — Understand what was modified (files, scope, intent)
  2. Propose a conventional commit message — Format: type(scope): message
    • Types: feat, fix, test, refactor, docs, chore, perf, ci
    • Scope: affected area (e.g. engine, cursor, config)
    • Message: imperative, lowercase, no period
  3. Stage if needed — Stage relevant files (ask before git add . if many files)
  4. Commit — Run git commit -m "..." with the proposed message

If the user requests edits to the message, adjust and re-commit. Do not amend without explicit request.

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 · 22 lines · 8 tokens per session scan A 3e6dcc5871ad

Subscribe to this mod's changes

commit is a command published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 229 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-09-03.