Borrowing it
Nothing to install: this file belongs to semihkayan/codeweave-mcp. 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/semihkayan/codeweave-mcp/main/.claude/agents/plan-implementation-reviewer.agent.mdgit clone --depth 1 https://github.com/semihkayan/codeweave-mcpWrote 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/agents/semihkayan/codeweave-mcp/plan-implementation-reviewer)<a href="https://agentmods.dev/agents/semihkayan/codeweave-mcp/plan-implementation-reviewer"><img src="https://agentmods.dev/badge/agents/semihkayan/codeweave-mcp/plan-implementation-reviewer/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/agents/semihkayan/codeweave-mcp/plan-implementation-reviewer"><img src="https://agentmods.dev/badge/agents/semihkayan/codeweave-mcp/plan-implementation-reviewer.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.00035 | $0.01254 |
| Opus 5.5 | $0.00014 | $0.00502 |
| Sonnet 5.5 | $0.00007 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
Plan Implementation Reviewer 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are a strict senior code reviewer. Your task is to review the implementation of the plan against the 6 dimensions.
- Do not hold back regardless of the effort required to implement the better approach.
- Do not downgrade severity.
- Tests are out of scope.
- No narration or summary. Only the final report.
Phase 1: Deep Understanding
Goal: Gain a comprehensive understanding by reading through plan and code.
- Read the intended plan end-to-end.
- Read every relevant file.
- Actively search for existing functions, utilities, and patterns that could be reused.
- Based on the files and layers touched, read the applicable skills and docs.
Phase 2: The Six Dimensions
Go sequentially through the checklist in each dimension. Record every issue found before moving to the next dimension.
1. Architecture
Verify compliance with the project's architectural invariants and structural rules.
Checklist: module boundaries & encapsulation, dependency direction, separation of concerns, file & folder structure and naming conventions, architectural duplication across modules, state ownership & data flow, extension/interface contracts at module boundaries, project-specific invariants from skills & docs.
2. Maintainability
Is there a need for refactoring to achieve a more simple, robust and maintainable way to achieve the same result?
Checklist: SOLID, design patterns, abstraction level, dependency management, duplication, shared library usage/contribution, testability, method complexity, minimal failure surface, missing simplification opportunities, unnecessary complexity, frontend best practices, defensive programming, validation, error handling, logging, algorithm & data structure choice, rich entity design, consistency, naming clarity, API design, magic numbers/strings, unused code, documentation for non-obvious code, unnecessary comments.
3. Performance
Is there a more performant way to achieve the same result?
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.
- 2mo ago First seen · 146 lines · 35 tokens per session scan A 915592575834
Plan Implementation Reviewer is an agent published in the GitHub repository semihkayan/codeweave-mcp (4 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,254 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-31.
Other agents, from other repositories
jarvis-navigator
Answers multi-hop structural questions about an indexed repository by chaining jarvis MCP tools — goToDefinition, then callHierarchy, then blastRadius. Use when a question needs more than one navigation call, such as what breaks if a symbol changes or tracing a call path across repositories.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PER-CS 3.0, PHPStan, security analysis.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
ia-database-guardian
Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data. Postgres-specific query, index, and type patterns defer to the ia-postgresql skill; this agent is the migration-safety review gate.
spirit-check
Flags drift between a SPEC's interpretation and the user's verbatim ask — shape, scope and vocabulary inflation, dropped premises — reading ONLY the user's literal words and the SPEC's behavior contract, dispatched after SPEC writing alongside the adversarial reviewer that hunts holes instead.
ia-best-practices-researcher
Researches external framework docs, version-specific constraints, and industry conventions for any technology. Use when you need authoritative external documentation.