Borrowing it
Nothing to install: this file belongs to MarcusJellinghaus/mcp-workspace. 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-workspace/main/.claude/skills/implementation_needs_rework/SKILL.mdgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspaceWrote 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-workspace/implementation_needs_rework)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/implementation_needs_rework"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/implementation_needs_rework/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-workspace/implementation_needs_rework"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/implementation_needs_rework.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00257 |
| Opus 5.5 | $0.00006 | $0.00103 |
| Sonnet 5.5 | $0.00003 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
implementation_needs_rework 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- implementation_needs_rework — 100% identical, 0 lines differ
- implementation_needs_rework — 100% identical, 0 lines differ
What it actually says
Return to plan-ready after major review issues
Transitions the issue back to plan-ready status for re-implementation when code review identifies major issues that cannot be fixed with minor changes.
When to Use
| Situation | Action |
|---|---|
| Minor fixes | Fix directly, re-run /implementation_review or /implementation_review_supervisor |
| Major issues | This command (after /implementation_new_tasks + /commit_push) |
| Approved | /implementation_approve |
Prerequisites
- New implementation steps created (
/implementation_new_tasks) - Changes committed and pushed (
/commit_push)
Instructions
mcp-coder gh-tool set-status status-05:plan-ready
Confirm the status change was successful. If it fails, report the error. Do not use --force unless explicitly asked.
Next Steps
Run mcp-coder implement to process the new steps, then /implementation_review or /implementation_review_supervisor.
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 · 36 lines · 14 tokens per session scan A 72b6b6ecaf70
implementation_needs_rework is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (48 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 257 once invoked, about $0.0001 per session on Opus 5.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
gitnexus-pr-review
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?".
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
code-review
Reviews a supplied code path or diff for correctness, security, maintainability, and style without executing or modifying it.
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…