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 skills/marcusjellinghaus/mcp-tools-py/commit_pushnpx skills add MarcusJellinghaus/mcp-tools-py --skill commit_pushgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-pyWhat 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.00012 | $0.00344 |
| Opus 5 | $0.00006 | $0.00172 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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.
This is a copy
100% identical to commit_push — 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.
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
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 · 45 lines · 12 tokens per session scan A 88b9119818cb
commit_push is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-py (18 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 344 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to commit_push, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
test-generator
Generate pytest test cases for Python functions and classes.
test-guide
Test-writing guide for Backend.AI — propose success/exception/edge scenarios first, refine them with the user, then implement while reporting per-scenario verification status. Covers fixtures, withtables, mock repositories, pants test, optional TDD cadence.
simulate-contracts
Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.
model-data-schema
Author the persistence schema as a binding contract from the captured external shapes and the interview — before any test stub is written.
author-test-stubs
Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.
derive-source-stubs
Derive the source stub files (.pyi) from the reviewed tests — every type the tests reference gets a definition.