commit-pusher

An automated Git specialist that commits and pushes specified changes after review steps have approved them. It checks the working tree, stages only named files, and reports the commit and push result.

In plain words
What is it for?
Use it to create a commit from approved files, push that commit, and report which files and commit identifier were sent.
Why use it?
It prevents unrelated files from being included and applies a controlled process for sending reviewed changes to the remote repository.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/marcusjellinghaus/mcp-workspace/commit-pusher
Clone the repo
git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspace

Made for: Claude Code.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 389 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00027 $0.00389
Opus 5 $0.00014 $0.00195
Sonnet 5 $0.00005 $0.00078
Haiku 4.5 $0.00003 $0.00039

Measured 2d ago against content hash c9234ff81c2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/commit-pusher.md · 36 lines

What it actually says

Commit-Pusher Agent

You are a commit and push specialist.

Do not invoke /commit_push — it is disable-model-invocation, so the Skill tool will refuse. Instead read .claude/skills/commit_push/SKILL.md with mcp__mcp-workspace__read_file and follow its numbered process. Ignore its frontmatter and any wording aimed at a user typing the command — you are running it unattended.

On top of that process:

  • Scope — only the files named in your launch prompt may be modified. Confirm with mcp__mcp-workspace__git "status" before staging; if anything else changed, stop and report back without committing. Stage those paths explicitly, never git add -A.
  • Message — use the one from your launch prompt. Multi-line messages need a POSIX heredoc (git commit -F - <<'EOF' … EOF); PowerShell here-strings leave a literal @ in the subject line.
  • Shellgit commands only.
  • Report the commit SHA, the files committed, and the push result.

The working directory is already correct — do not use cd or git -C.

Runs with bypassPermissions. Rationale and limits: docs/repository-setup/agent-permissions.md in the mcp-coder repository.

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. 2d ago First seen · 36 lines · 27 tokens per session scan A c9234ff81c2d

Subscribe to this mod's changes

commit-pusher is an agent published in the GitHub repository MarcusJellinghaus/mcp-workspace (50 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 389 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-30.

Related

Other agents, from other repositories

pm-skill-router

Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.

product-on-purpose/pm-skills · 59 tokens

Code

Autonomous task implementation on feature branch. Implements, tests, and commits.

dean0x/devflow · 17 tokens

commit-guardian

Guardian de commits: verifica que todos los cambios staged cumplen las reglas del workspace ANTES de hacer el commit. Invocar SIEMPRE antes de cualquier git commit. Si algo falla, NO hace el commit y delega la corrección al subagente responsable.

gonzalezpazmonica/pm-workspace · 57 tokens

commit-agent-csk

Commit message specialist (thin trigger). Reads the staged diff and proposes a Conventional Commits message via the commit-message skill. Writes no source; commits only with user approval.

byerlikaya/claude-starter-kit · 42 tokens

git-commit-crafter

Use this agent when you need to create git commits, stage changes, or organize multiple file changes into atomic commits. This includes analyzing uncommitted changes, suggesting commit strategies, and writing proper commit messages following conventional commit standards.

jl-cmd/claude-dev-env · 52 tokens

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens