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 supportersimulator/3-surgeons --skill pre-implementation-reviewgit clone --depth 1 https://github.com/supportersimulator/3-surgeonsWrote 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/supportersimulator/3-surgeons/pre-implementation-review)<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/pre-implementation-review"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/pre-implementation-review/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/supportersimulator/3-surgeons/pre-implementation-review"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/pre-implementation-review.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.00024 | $0.00750 |
| Opus 5 | $0.00012 | $0.00375 |
| Sonnet 5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
pre-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 8d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Implementation Review
Purpose
The gap between "good plan" and "good implementation" is where most bugs are born. This gate ensures the plan survives adversarial scrutiny BEFORE any code is written.
Auto-Invocation Trigger
Invoke when transitioning from planning to implementation — specifically:
- After
writing-plansskill produces an implementation plan - Before
executing-plansskill begins work - Before any multi-file implementation begins
- When a design doc exists and coding is about to start
Checklist
You MUST create a TodoWrite task for each step:
-
Sentinel scan on the implementation plan — run sentinel with the plan description as content. This catches complexity risks the planning phase may have introduced.
-
Cross-exam the plan with all 3 surgeons — focus question: "What will break when we implement this?" Not "is this a good idea?" (that was architectural-gate's job) but "what will go wrong during execution?"
-
Counter-position: argue why this plan will FAIL — invoke the counter-position skill. The claim is "this implementation plan will succeed." Steelman why it will not.
-
Verify gains-gate passes — infrastructure must be healthy before starting. Do not build on broken foundations.
-
Create explicit rollback strategy — before writing code, document how to undo the changes if they go wrong. This forces thinking about reversibility.
-
Present review results — summarize findings from steps 1-5. Proceed only with approval. If surgeons raised critical concerns, those must be addressed in the plan before implementation begins.
What the Cross-Exam Should Focus On
The cross-exam question for pre-implementation is specifically:
We are about to implement the following plan:
[plan summary]
Focus your analysis on:
1. What will break during implementation?
2. What dependencies or ordering constraints are missing?
3. What edge cases does the plan not address?
4. Are there simpler approaches the plan overlooked?
5. What tests should exist BEFORE implementation starts?
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.
- 8d ago First seen · 88 lines · 24 tokens per session scan A e1c2664ba7a5
pre-implementation-review is a skill published in the GitHub repository supportersimulator/3-surgeons (2 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 750 once invoked, about $0.0001 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-31.
Other skills, from other repositories
gh-pr-review
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks…
review-spd
Findings-first code review workflow for AI coding agents. Use when the user asks to review uncommitted changes, commits in a date range, or a branch compared to the main branch / PR-style diff. Focuses on bugs, regressions, correctness risks, missing tests, security/data-safety issues, and other behavior-changing…
karpathy-guidelines
A set of coding guidelines based on observations about common mistakes made by language models. It emphasizes simple solutions, small targeted edits, clear assumptions, and checkable results.
gh-cli
Patterns for invoking the GitHub CLI (gh v2.100.0+) from agents. Use when the task mentions GitHub, gh, pull requests/PRs, issues, releases, gists, Actions/workflow runs, forks, repo cloning, reviews, or you need exact gh commands. Covers pagination, repo targeting, search vs list, discussions, projects, rulesets…
code-review
A single-pass review method for examining a code change, branch, or pull request. A pull request is a proposed change for review before it is merged into a shared codebase.
simplify
Behavior-preserving code simplification — reduce complexity without changing what the code does. Use when the task mentions "simplify", "reduce complexity", "too clever", "hard to read", "reduce nesting", or after a feature lands and the code needs polishing. Oracle analyzes (read-only), light-orchestrator applies the…