mcp-workspace: Skill for Claude Code

.claude/skills/commit_push/SKILL.md

commit_push is a skill for Claude Code from MarcusJellinghaus/mcp-workspace. It costs 12 tokens per session (344 once invoked), scanned A, original, MIT.

A workflow for formatting code, reviewing the changes, creating a Git commit, and sending the branch to a remote repository.

In plain words
What is it for?
Use it when finished work needs formatting, a change review, a conventional commit such as a feature or fix, and a push to the remote Git repository.
Why use it?
It gives routine code delivery a consistent order and commit-message format, reducing missed checks before sharing changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

This is MarcusJellinghaus/mcp-workspace's own configuration. It tells Claude Code how to work on mcp-workspace 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-workspace configures →

Reuse

Borrowing it

Nothing to install: this file belongs to MarcusJellinghaus/mcp-workspace. 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-workspace/main/.claude/skills/commit_push/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspace

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/skills/marcusjellinghaus/mcp-workspace/commit_push/github.svg)](https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/commit_push)
Your own site
<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/commit_push"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/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/skills/marcusjellinghaus/mcp-workspace/commit_push"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/commit_push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 344 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00012 $0.00344
Opus 5.5 $0.00005 $0.00138
Sonnet 5.5 $0.00002 $0.00069
Haiku 4.5 $0.00001 $0.00034

Measured 1mo ago against content hash 88b9119818cb, 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

.claude/skills/commit_push/SKILL.md · 45 lines

What it actually says

Commit and Push Changes

Follow this process to commit and push your changes:

1. Format Code

Use mcp__mcp-tools-py__run_format_code to format all code (black + isort).

2. Review Changes

Use mcp__mcp-workspace__git with command "status" to check working directory state. Use mcp__mcp-workspace__git with command "diff" to review the changes.

3. Stage Changes

Stage all relevant changes (exclude any files that shouldn't be committed).

4. Commit

Create a commit with a clear, conventional commit message:

  • Use format: type(scope): description
  • Types: feat, fix, docs, style, refactor, test, chore
  • Keep summary under 50 characters
  • No Claude Code footer or attribution in commit message

5. Push

git push

If the branch doesn't exist on remote yet:

git push -u origin HEAD
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 · 45 lines · 12 tokens per session scan A 88b9119818cb

Subscribe to this mod's changes

commit_push is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (48 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 344 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-30.

Related

Other skills, from other repositories

papi-build

Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.

getpapi/papi · 26 tokens

papi-auto

Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.

getpapi/papi · 35 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…

cyanheads/pubmed-mcp-server · 109 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…

cyanheads/mcp-ts-core · 109 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…

cyanheads/ntfy-mcp-server · 109 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…

cyanheads/secedgar-mcp-server · 109 tokens