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 agentmods add skills/marcusjellinghaus/mcp-workspace/implementation_reviewnpx skills add MarcusJellinghaus/mcp-workspace --skill implementation_reviewgit 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_review)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/implementation_review"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/implementation_review.svg" alt="Measured on agentmods" 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.00355 |
| Opus 5 | $0.00004 | $0.00178 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
implementation_review 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 6d 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_review — 97% identical, 3 lines differ
- implementation_review — 97% identical, 0 lines differ
What it actually says
Implementation Review (Code Review)
First, ensure we're up to date:
Call mcp__mcp-workspace__git with command "fetch" and args ["origin"].
Use mcp__mcp-workspace__git with command "status" to check working directory state.
Call mcp__mcp-workspace__check_branch_status.
Confirm and display the current feature branch name.
Then run the code review:
Code Review Request
Use mcp__mcp-workspace__git with command "diff" to get the changes to review.
No need to run all checks; do not use pylint warnings. Feel free to further analyse any mentioned files and/or the file structure.
Focus Areas:
- Logic errors or bugs
- Tests for
__main__functions should be removed (not needed) - Unnecessary debug code or print statements
- Code that could break existing functionality
- Compliance with existing architecture principles, see
docs/architecture/architecture.md
Output Format:
- Summary - What changed (1-2 sentences)
- Critical Issues - Must fix before merging
- Suggestions - Nice to have improvements
- Good - What works well
Do not perform any action. Just present the code review.
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.
- 6d ago First seen · 44 lines · 8 tokens per session scan A 734fe923c034
implementation_review is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (50 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 355 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
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?".
my-complex-skill
Production-ready Model Context Protocol (MCP) server for multi-agent AI consultations (Codex, Claude, Anti-Gravity, Mimo) with Minimax-M3 consensus synthesis.
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
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".
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".