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 issue_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/issue_approve)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-py/issue_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/issue_approve.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00494 |
| Opus 5 | $0.00004 | $0.00247 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
issue_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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- issue_approve — 94% identical, 4 lines differ
What it actually says
Approve Issue
Approve the current issue to transition it to the next status in the workflow.
Resolve Issue Number
The user may provide an issue number as the argument (available as $ARGUMENTS).
If no issue number is provided:
- Check if the issue number is known from prior
/issue_analyseor/issue_createin this conversation - Read
.vscodeclaude_status.txtand extract the issue number from theIssue #NNNline - If still unknown, ask the user
Cross-Repo Issues
If a --repo owner/repo flag was given, append it to every gh command below, and fetch the
issue with gh issue view <issue_number> --repo owner/repo via Bash —
mcp__mcp-workspace__github_issue_view only reaches the current repository.
Instructions
-
Fetch the issue to confirm it exists: Call
mcp__mcp-workspace__github_issue_viewwith the issue number (orgh issue viewfor cross-repo). -
Validate that the issue is ready for approval:
- Issue has been analyzed/discussed
- Requirements are clear
- No blocking questions remain
-
Comment
/approveon the issue (use MSYS_NO_PATHCONV to prevent Windows Git Bash path conversion):
MSYS_NO_PATHCONV=1 gh issue comment <issue_number> --body "/approve"
This triggers the GitHub Action to promote the issue status (e.g., status-01:created → status-02:awaiting-planning).
Note: This skill has disable-model-invocation — it can only be run by the user typing /issue_approve. If you need this skill as a follow-up, tell the user: "Please run /issue_approve to proceed."
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.
- 4d ago Changed · +6 lines f4ed62be3cda
- 8d ago First seen · 43 lines · 8 tokens per session scan A 2a7e0f64ec04
issue_approve is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-py (18 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 494 once invoked, about $0.0000 per session on Opus 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.
Other skills, from other repositories
metagit-cli
CLI-only shortcuts for metagit agents — workspace catalog, discovery, prompts, sync, layout, and config. Use instead of MCP or HTTP API when operating from a shell or agentmode session.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
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…
daemon-loop
Autonomous recurring agent tasks — converts workflows into persistent background daemons that run on intervals. Stolen from Boris Cherny's Claude Code /loop pattern (2026-03-31).
write-workflow-as-code
MUST use when writing or modifying Windmill Workflow-as-Code scripts using workflow, task, step, sleep, approvals, taskScript, taskFlow, taskscript, or taskflow.