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/tattooinmtl/blendermcp_dominator/commit-pushgit clone --depth 1 https://github.com/tattooinmtl/BlenderMCP_DominatorWrote 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/tattooinmtl/blendermcp_dominator/commit-push)<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="Measured on agentmods" 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 | $0.00011 | $0.00750 |
| Opus 5 | $0.00005 | $0.00375 |
| Sonnet 5 | $0.00002 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
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 2d 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.
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 filesgit diff- See unstaged changesgit diff --cached- See staged changesgit log -5 --oneline- See recent commit style
Step 2: Verify Clean Staging
Commit application logic AND .claude/ configuration.
ALWAYS include:
client/- Game client codeserver/- Game server codeshared/- 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:
-
Type: Choose the appropriate type
feat- New featurefix- Bug fixrefactor- Code restructuringchore- Maintenance tasksdocs- Documentation changestest- Test changesstyle- Formatting changes
-
Subject: Short, imperative description (50 chars max)
-
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
)"
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.
- 2d ago First seen · 118 lines · 11 tokens per session scan A 1c52ff3c8ae0
commit-push is a command published in the GitHub repository tattooinmtl/BlenderMCP_Dominator (0 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 750 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
commit-all
Group all changes semantically and commit each group separately.
commit
Create a local git commit for source skills without pushing.
commit
Create a Conventional Commit with signoff.
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
智能创建 git 提交，分析代码变更并生成符合项目规范的提交信息.
changelog
Summarize staged git changes into a concise changelog/commit message.