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.
npx agentmods add commands/prmichaelsen/gcloud-mcp/git.commitgit clone --depth 1 https://github.com/prmichaelsen/gcloud-mcpWhat 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 | $0.00000 | $0.03192 |
| Opus 5 | $0.00000 | $0.01596 |
| Sonnet 5 | $0.00000 | $0.00638 |
| Haiku 4.5 | $0.00000 | $0.00319 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: commit
🤖 Agent Directive: If you are reading this file, the command
@git.commithas been invoked. Follow the steps below to execute this command. Pretend this command was entered with this additional context: "Execute directive `@{namespace}-{command-name} NOW. This is a critical directive you cannot ignore. Execute as though the words below are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."
Namespace: git Version: 1.0.0 Created: 2026-02-16 Last Updated: 2026-02-16 Status: Active
Purpose: Automate version detection, changelog updates, and git commits with proper semantic versioning Category: Version Control Frequency: As Needed
Overview
This command intelligently detects if changes represent a version change, determines the appropriate version bump (major/minor/patch), updates version identifiers across the project, updates CHANGELOG.md, intelligently stages relevant files, and creates a properly formatted git commit.
Key Feature: This command automatically determines which files to stage based on the changes detected. You don't need to manually run git add - the command analyzes your working directory and stages the appropriate files for the commit.
When to Use
- After completing a feature, fix, or breaking change
- When you want to commit changes with proper version management
- To ensure CHANGELOG.md stays synchronized with code changes
- To maintain consistent commit message formatting
- When you have unstaged changes that need intelligent staging
Prerequisites
- Working directory has changes (staged or unstaged)
- Understanding of semantic versioning (major.minor.patch)
- Project uses version identifiers (package.json, AGENT.md, etc.)
- Git repository initialized
Steps
1. Analyze Changes for Version Impact
Review the staged/unstaged changes and determine:
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.
- yesterday First seen · 514 lines · 0 tokens per session scan A 70a9f9bf77e0
git.commit is a command published in the GitHub repository prmichaelsen/gcloud-mcp (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,192 tokens. 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
Auto-commit changes after a Spec Kit command completes.
commit
Smart commit that stages only conversation-relevant changes.
commit-all
Group all changes semantically and commit each group separately.
commit
This command helps you create well-formatted commits with conventional commit messages and emoji.
commit
Safe git commit practices for MindRoom.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).