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 implement_directgit 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/implement_direct)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-py/implement_direct"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/implement_direct/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/implement_direct"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/implement_direct.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.00008 | $0.00709 |
| Opus 5.5 | $0.00003 | $0.00284 |
| Sonnet 5.5 | $0.00002 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
implement_direct 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
86% identical to implement-direct — 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Direct
Implement a small, well-defined issue directly — no planning phase, no task tracker.
Resolve Issue Number
The user may provide an issue number as the argument (available as $ARGUMENTS).
If no issue number is provided:
- Read
.vscodeclaude_status.txtand extract the issue number from theIssue #NNNline - If the file doesn't exist or has no issue number, ask the user
Steps
-
Fetch issue details Call
mcp__mcp-workspace__github_issue_viewwith the issue number. Read the issue title, description, and acceptance criteria carefully. -
Checkout/create issue branch
mcp-coder gh-tool checkout-issue-branch <issue_number> -
Understand context
- Read relevant source files referenced in the issue
- Understand the existing code patterns and conventions
- Identify the minimal set of changes needed
-
Implement changes
- Make the required code changes directly
- Follow existing code patterns and conventions
- Keep changes focused and minimal — only what the issue requires
-
Run quality checks
mcp__mcp-tools-py__run_pylint_check— fix all issuesmcp__mcp-tools-py__run_pytest_check(withextra_args: ["-n", "auto"]) — fix all failuresmcp__mcp-tools-py__run_mypy_check— fix all issuesmcp__mcp-tools-py__run_ruff_check— fix all issues
-
Format code Use
mcp__mcp-tools-py__run_format_codeto format all code (black + isort). -
Update issue status
mcp-coder gh-tool set-status status-07:code-review -
Suggest follow-up steps
/commit_push— commit and push changes/check_branch_status— verify branch is clean/implementation_review— request a review of the implementation
Scope Guidance
This skill is designed for small, well-defined issues that can be implemented in a single pass. If the issue is complex or involves multiple components, recommend the full workflow instead:
/create_plan— create a detailed implementation plan/implement— implement the plan step by step
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 · 75 lines · 8 tokens per session scan A f21e8ae3fac9
implement_direct is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-py (19 stars, last pushed 8d ago), licensed MIT. It adds 8 tokens to every session and 709 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to implement-direct, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
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…
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.
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.