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/implementation_approvenpx skills add MarcusJellinghaus/mcp-tools-py --skill implementation_approvegit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-pyWrote 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/skills/marcusjellinghaus/mcp-tools-py/implementation_approve)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-py/implementation_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/implementation_approve.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.1 | $0.00009 | $0.00304 |
| Opus 5 | $0.00005 | $0.00152 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
implementation_approve 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 6d 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
92% identical to implementation_approve — 7 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
Approve Implementation
Approve the implementation and transition the issue to PR-ready state.
Instructions:
-
Run branch-status check using
mcp__mcp-workspace__check_branch_status. -
If
branch-statusreports a base branch other thanmain, ask the user to confirm this is intentional before proceeding. -
Only if the branch-status check passes (exit code 0), run the set-status command and confirm it succeeded:
mcp-coder gh-tool set-status status-08:ready-pr
Note: If the branch-status check fails, report the failures to the user and do not set the label. If the set-status command fails, report the error to the user. Do not use --force unless explicitly asked.
Effect: Changes issue status from status-07:code-review to status-08:ready-pr.
- After the label is set, poll for the PR to be created and pass CI. This runs in the background — the background process creates the PR while it polls (up to 600s):
Use
mcp__mcp-workspace__check_branch_statusto poll for the PR and CI status.
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.
- 6d ago First seen · 29 lines · 9 tokens per session scan A e22cbb90ed65
implementation_approve is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-py (18 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 304 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to implementation_approve, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
test-quality
Test quality bar for this repo. Read when writing, reviewing, or designing tests — covers naming, abstraction level, assertions, determinism, and the process for agent-driven test work.
idapython
IDA Pro Python scripting for reverse engineering. Use when writing IDAPython scripts, analyzing binaries, working with IDA's API for disassembly, decompilation (Hex-Rays), type systems, cross-references, functions, segments, or any IDA database manipulation. Covers ida modules (50+), idautils iterators, and common…
vibeue
Unreal Engine 5 development using the VibeUE Python API. Use when working in Unreal Engine — blueprints, state trees, materials, actors, landscapes, animation, niagara, widgets, sound, foliage, gameplay tags, enhanced input, skeletons, PCG (procedural content generation), and more. VibeUE is an extension of Unreal's…
test-generator
Generate pytest test cases for Python functions and classes.
n8n-code-python
Write Python code in n8n Code nodes. Use when writing Python in n8n, using input/json/node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes. Use this skill when the user specifically requests Python for an n8n Code node. Note — JavaScript is recommended for 95% of use…
touchdesigner-self-debug
A generic workflow for self-starting TouchDesigner via computer-use (or an already-running instance), loading mcpwebserverbase.tox, and verifying any TD-side Python change (td/modules/) directly from the Textport — reading back real TD runtime values and reconciling them. Use after changing TD-side code in the…