mcp-tools-sql: Agent for Claude Code

.claude/agents/commit-pusher.md

commit-pusher is an agent for Claude Code from MarcusJellinghaus/mcp-tools-sql. It costs 27 tokens per session (389 once invoked), scanned A, a copy of commit-pusher, MIT.

An automated coding agent that commits and pushes specified changes to a Git repository. It checks that only the allowed files changed and reports the commit and push result.

In plain words
What is it for?
Use it after implementation or plan review to stage named files, create the requested commit, and push the current branch.
Why use it?
It reduces the risk of committing unrelated files when another review workflow has approved a precise set of changes.

Agent for Claude Code

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

This is MarcusJellinghaus/mcp-tools-sql's own configuration. It tells Claude Code how to work on mcp-tools-sql itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-tools-sql configures →

Reuse

Borrowing it

Nothing to install: this file belongs to MarcusJellinghaus/mcp-tools-sql. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/MarcusJellinghaus/mcp-tools-sql/main/.claude/agents/commit-pusher.md
Clone the repo
git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-sql

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/marcusjellinghaus/mcp-tools-sql/commit-pusher/github.svg)](https://agentmods.dev/agents/marcusjellinghaus/mcp-tools-sql/commit-pusher)
Your own site
<a href="https://agentmods.dev/agents/marcusjellinghaus/mcp-tools-sql/commit-pusher"><img src="https://agentmods.dev/badge/agents/marcusjellinghaus/mcp-tools-sql/commit-pusher/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-pusher

Your own site · 80×15
<a href="https://agentmods.dev/agents/marcusjellinghaus/mcp-tools-sql/commit-pusher"><img src="https://agentmods.dev/badge/agents/marcusjellinghaus/mcp-tools-sql/commit-pusher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00027 $0.00389
Opus 5.5 $0.00011 $0.00156
Sonnet 5.5 $0.00005 $0.00078
Haiku 4.5 $0.00003 $0.00039

Measured 1mo ago against content hash c9234ff81c2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

100% identical to commit-pusher — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.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.
  • Shell — git 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. 1mo 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-tools-sql (2 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 389 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to commit-pusher, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

secrets-detector

Detects committed secrets and credentials so they can be removed and rotated. Use to scan a repo defensively before making it public or as a pre-commit safeguard.

JosephHampton/awesome-gemini-cli-subagents · 38 tokens

plastic-node-work

Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.

zalom/plastic · 65 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

commit

Runs the auto-commit skill.

mystilleef/spae-framework · 8 tokens

git-specialist

Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.

fmflurry/settings-opencode · 62 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens