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 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/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.
<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="Reviewed on agentmods" width="80" 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.5 | $0.00004 | $0.00122 |
| Sonnet 5.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 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.
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.
- 1mo 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 (19 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.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
x-reader
Read source URLs from X/Twitter, articles, YouTube, Bilibili, podcasts, WeChat, Xiaohongshu, Telegram, RSS, and the open web. Use when the user provides a link and wants the original content, evidence, transcript, summary, or source-grounded analysis.
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…
analyzer
Turn source content or a verified transcript into a structured, evidence-grounded analysis with key insights, risks, and action items.
mcp-tools-reference
MUST READ before first MCP tool call in a session. Complete Envoy tool catalog with parameters and usage.
td-api-reference
MUST READ before writing TD Python via executepython, setdatcontent, or editdatcontent, and before any heavy build. Parameters, storage, operators, referencing, threading, cook model, heavy-build safety caps.
brief
Compile a conversational request into an Embody task brief (briefs/.md): skills to load, discovered anchors, verifiable success criteria, and gates -- then execute the work from that contract. User-invoked via /brief.