commit-push

commit-push is a command for Claude Code from tattooinmtl/BlenderMCP_Dominator. It costs 11 tokens per session (750 once invoked), scanned A, original, MIT.

A Git workflow command that reviews repository changes, stages the intended files, creates a commit, and pushes it to the remote repository.

In plain words
What is it for?
Use it to inspect status and diffs, follow the repository’s recent commit style, stage approved changes, and publish them.
Why use it?
It reduces missed changes and helps keep generated files, secrets, and temporary files out of commits.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions Claude Code.

Good fit Use it to inspect status and diffs, follow the repository’s recent commit style, stage approved changes, and publish them.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/tattooinmtl/blendermcp_dominator/commit-push
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.

Clone the repo
git clone --depth 1 https://github.com/tattooinmtl/BlenderMCP_Dominator

Made for: Claude Code.

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-push

README.md
[![agentmods](https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/commit-push/github.svg)](https://agentmods.dev/commands/tattooinmtl/blendermcp_dominator/commit-push)
Your own site
<a href="https://agentmods.dev/commands/tattooinmtl/blendermcp_dominator/commit-push"><img src="https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/commit-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.

agentmods 80×15 button for commit-push

Your own site · 80×15
<a href="https://agentmods.dev/commands/tattooinmtl/blendermcp_dominator/commit-push"><img src="https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/commit-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 750 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00011 $0.00750
Opus 5.5 $0.00004 $0.00300
Sonnet 5.5 $0.00002 $0.00150
Haiku 4.5 $0.00001 $0.00075

Measured 1mo ago against content hash 1c52ff3c8ae0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit-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.

addon/blender_mcp_addon/dominator/.claude/commands/commit-push.md · 118 lines

How it starts

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

Commit and Push Workflow

You are committing and pushing code changes. Follow this process carefully.

Step 1: Analyze Changes

Run these commands in parallel:

  • git status - See all modified, staged, and untracked files
  • git diff - See unstaged changes
  • git diff --cached - See staged changes
  • git log -5 --oneline - See recent commit style

Step 2: Verify Clean Staging

Commit application logic AND .claude/ configuration.

ALWAYS include:

  • client/ - Game client code
  • server/ - Game server code
  • shared/ - Shared types and constants
  • .claude/ - Claude Code configuration (commands, skills, hooks, settings)
  • docs/ - Documentation
  • Config files (package.json, tsconfig.json, etc.)

NEVER include:

  • node_modules/
  • dist/
  • build/
  • .idea/
  • __pycache__/
  • .claude/reflections/ - Session reflection logs (local only)
  • Any .env* files
  • Debug logs, temporary scripts

If unwanted files are staged, remove them:

git rm -r --cached <unwanted-path>

Step 3: Stage Changes

Stage ALL changes first, then exclude unwanted files:

git add -A
git reset HEAD node_modules/ dist/ build/ __pycache__/ .claude/hooks/__pycache__/ .claude/reflections/ 2>/dev/null || true

Important: Commit everything including .claude/ config. Do NOT cherry-pick files.

Step 4: Write Commit Message

Analyze ALL changes and write a precise commit message:

  1. Type: Choose the appropriate type

    • feat - New feature
    • fix - Bug fix
    • refactor - Code restructuring
    • chore - Maintenance tasks
    • docs - Documentation changes
    • test - Test changes
    • style - Formatting changes
  2. Subject: Short, imperative description (50 chars max)

  3. Body: If changes are non-trivial, add bullet points explaining:

    • What was changed
    • Why it was changed
    • Any important details

Step 5: Commit

Use HEREDOC format for the commit message:

git commit -m "$(cat <<'EOF'
type: short description

- Detail 1
- Detail 2
EOF
)"

Read the full file on GitHub · 118 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. 1mo ago First seen · 118 lines · 11 tokens per session scan A 1c52ff3c8ae0

Subscribe to this mod's changes

commit-push is a command published in the GitHub repository tattooinmtl/BlenderMCP_Dominator (1 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 750 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.