Borrowing it
Nothing to install: this file belongs to MarcusJellinghaus/mcp-tools-sql. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MarcusJellinghaus/mcp-tools-sql/main/.claude/skills/implementation_approve/SKILL.mdgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-sqlWrote 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-sql/implementation_approve)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/implementation_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/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-sql/implementation_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/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.00266 |
| Opus 5.5 | $0.00004 | $0.00106 |
| Sonnet 5.5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
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
89% identical to implementation_approve — 5 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: Call
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, 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, call
mcp__mcp-workspace__check_branch_statusagain to verify CI and PR 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 863bd1268d23
implementation_approve is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 266 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to implementation_approve, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…