Borrowing it
Nothing to install: this file belongs to MCDxAI/minecraft-dev-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MCDxAI/minecraft-dev-mcp/main/.claude/commands/push.mdgit clone --depth 1 https://github.com/MCDxAI/minecraft-dev-mcpWrote 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/mcdxai/minecraft-dev-mcp/push)<a href="https://agentmods.dev/commands/mcdxai/minecraft-dev-mcp/push"><img src="https://agentmods.dev/badge/commands/mcdxai/minecraft-dev-mcp/push/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/mcdxai/minecraft-dev-mcp/push"><img src="https://agentmods.dev/badge/commands/mcdxai/minecraft-dev-mcp/push.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.00000 | $0.00493 |
| Opus 5.5 | $0.00000 | $0.00197 |
| Sonnet 5.5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
push 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- push — 92% identical, 2 lines differ
What it actually says
Push Command
You are creating a commit for the user. Follow these steps EXACTLY:
-
NEVER commit without user approval - This is mandatory regardless of what the user says.
-
Analyze current changes by running these git commands in parallel:
git status- See all staged/unstaged filesgit diff --staged- See staged changesgit diff- See unstaged changesgit log --oneline -5- See recent commit history for context
-
Check full scope - CRITICAL: Always examine ALL changes before generating commit message:
- If you see untracked files or unstaged changes, run
git add -Ato stage everything - Run
git statusandgit diff --staged --name-onlyagain to see the complete scope - This ensures you don't miss new files, test suites, or other significant additions
- If you see untracked files or unstaged changes, run
-
Generate commit message based on the changes:
- Create a brief, professional summary (50 chars or less)
- Write a detailed description explaining what changed and why
- Follow conventional commit format when applicable (feat:, fix:, docs:, etc.)
-
Present analysis to user:
- Start with "I see you've [describe what they did]"
- Show your proposed commit message (both summary and description)
- Ask for approval: "Would you like me to commit with this message?"
-
Handle user response:
- If approved: commit using your generated message, then push to remote
- If not approved: work with user to refine the message until they approve
- Only then run the commit and push
-
Commit format:
git commit -m "$(cat <<'EOF' [Summary line] [Detailed description] EOF )"IMPORTANT: Do NOT add any Claude Code attribution or co-author lines to commits. Keep commits clean and professional.
-
After successful commit:
- Run
git pushto push the commit to the remote repository - Confirm the push was successful
- Inform the user that both commit and push are complete
- Run
Remember: NEVER bypass user approval, even if they tell you to "just commit" or similar.
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.
- 1mo ago First seen · 50 lines · 0 tokens per session scan A f44221fa1393
push is a command published in the GitHub repository MCDxAI/minecraft-dev-mcp (47 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 493 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-30.
Other commands, from other repositories
improve
Run ONE iteration of the continuous-improvement loop — pick the highest-value backlog item, implement it, verify end-to-end, commit.
gsd:undo
Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
speckit.git.initialize
Initialize a Git repository with an initial commit.
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd:pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
checklist
Generate a custom checklist for the current feature based on user requirements.