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.
git clone --depth 1 https://github.com/xonovex/platformWrote 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.
[](https://agentmods.dev/commands/xonovex/platform/git-commit)<a href="https://agentmods.dev/commands/xonovex/platform/git-commit"><img src="https://agentmods.dev/badge/commands/xonovex/platform/git-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.
<a href="https://agentmods.dev/commands/xonovex/platform/git-commit"><img src="https://agentmods.dev/badge/commands/xonovex/platform/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00011 | $0.00376 |
| Opus 5.5 | $0.00004 | $0.00150 |
| Sonnet 5.5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
git-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 10d 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.
What it actually says
/xonovex-core:git-commit - Auto-Commit with Smart Messages
Create a conventional commit from the changes; use --push only when publication is requested.
Arguments
/git-commit [message] [--type <type>] [--path <path>] [--remote <remote>] [--branch <branch>] [--push] [--dry-run] [--interactive]
message(optional): Commit description (if omitted, auto-generates and uses best suggestion)--type <type>(optional): Commit type (auto-detected if not provided)--path(optional): Directory path for git commands (defaults to current directory)--remote(optional): Git remote to push to (defaults to "origin")--branch(optional): Remote branch to push to (defaults to current branch)--push(optional): Push after committing--dry-run(optional): Preview without committing--interactive(optional): Show suggestions and prompt for selection instead of auto-committing
Delegation
Load the git-guide skill (plugin xonovex-core) and perform its commit operation with these arguments. The skill is the source of truth for the procedure, output format, and gotchas. Do not restate them.
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.
- 10d ago Changed · -1 lines ebf9b4003045
- 1mo ago First seen · 32 lines · 11 tokens per session scan A 01d6d19faa72
git-commit is a command published in the GitHub repository xonovex/platform (6 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 376 once invoked, about $0.0000 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.
Other commands, from other repositories
speckit.git.commit
Proxy for speckit.git.commit.md.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
commit.en
Commit the current changes to Git.
commit.zh-CN
A command for creating a Git commit, which is a saved checkpoint of changes in a Git project.