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 RobinNorberg/oh-my-copilot --skill deep-reviewgit clone --depth 1 https://github.com/RobinNorberg/oh-my-copilotWrote 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/robinnorberg/oh-my-copilot/deep-review)<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/deep-review"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/deep-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/robinnorberg/oh-my-copilot/deep-review"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/deep-review.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.00017 | $0.02059 |
| Opus 5 | $0.00009 | $0.01030 |
| Sonnet 5 | $0.00003 | $0.00412 |
| Haiku 4.5 | $0.00002 | $0.00206 |
Grade A, and why
deep-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.
How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- User wants thorough multi-perspective code review:
/deep-review,--deep - PR or changeset is large (10+ files) and benefits from specialized analysis
- Changes touch security-sensitive code (auth, payments, API endpoints)
- User wants false-positive filtering on review findings </Use_When>
<Do_Not_Use_When>
- Quick review of a small change (1-3 files) — use code-reviewer agent directly
- User only wants security-specific review — use security-reviewer agent directly
- User wants a style-only review — use code-reviewer with model=haiku </Do_Not_Use_When>
<Why_This_Exists> Single-pass code reviews often miss issues or produce false positives because one reviewer tries to cover all concerns (security, quality, architecture) simultaneously. Deep Review separates concerns into specialized passes where each reviewer focuses on their domain, then adds a validation pass that filters false positives — producing higher-quality, actionable findings. </Why_This_Exists>
<Execution_Policy>
- Passes 1-3 MUST run in parallel (independent concerns)
- Pass 4 runs sequentially after passes 1-3 complete (depends on their output)
- Each pass uses the appropriate specialist agent
- Findings include validationStatus after pass 4
- Output is a consolidated markdown report </Execution_Policy>
-
Pass 1 - Security (parallel): Spawn security-reviewer agent
Task(subagent_type="oh-my-copilot:security-reviewer", model="sonnet", name="security-pass", prompt=" SECURITY REVIEW PASS for deep-review. Review the following changes for security vulnerabilities: - OWASP Top 10 categories - Hardcoded secrets - Injection vulnerabilities (SQL, XSS, command injection) - Authentication/authorization issues - Input validation gaps Output each finding as: FINDING: - severity: CRITICAL|HIGH|MEDIUM|LOW - category: security - subcategory: [OWASP category] - file: [file:line] - title: [brief title] - description: [detailed description] - suggestedFix: [how to fix] END_FINDING Scope: [insert scope/diff here] ") -
Pass 2 - Quality (parallel): Spawn code-reviewer agent
Task(subagent_type="oh-my-copilot:code-reviewer", model="sonnet", name="quality-pass", prompt=" QUALITY REVIEW PASS for deep-review. Review the following changes for code quality: - Logic defects (off-by-one, null handling, unreachable branches) - Error handling completeness - Performance issues (N+1 queries, O(n²) algorithms) - Anti-patterns and SOLID violations - Code duplication Output each finding as: FINDING: - severity: CRITICAL|HIGH|MEDIUM|LOW - category: quality - subcategory: [logic|error-handling|performance|anti-pattern|duplication] - file: [file:line] - title: [brief title] - description: [detailed description] - suggestedFix: [how to fix] END_FINDING Scope: [insert scope/diff here] ") -
Pass 3 - Structural (parallel): Spawn architect agent
Task(subagent_type="oh-my-copilot:architect", model="sonnet", name="structural-pass", prompt=" STRUCTURAL REVIEW PASS for deep-review. Review the following changes for architectural concerns: - API contract changes (breaking changes, versioning) - Backward compatibility - Coupling and cohesion issues - Abstraction leaks - Module boundary violations - Dependency direction violations Output each finding as: FINDING: - severity: CRITICAL|HIGH|MEDIUM|LOW - category: structural - subcategory: [api-contract|compatibility|coupling|abstraction|boundary|dependency] - file: [file:line] - title: [brief title] - description: [detailed description] - suggestedFix: [how to fix] END_FINDING Scope: [insert scope/diff here] ")
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 · 235 lines · 17 tokens per session scan A f603db0d0927
deep-review is a skill published in the GitHub repository RobinNorberg/oh-my-copilot (5 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 2,059 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-09-04.
Other skills, from other repositories
pr-review
Multi-dimensional review of a PR or feature branch in microsoft/win-dev-skills. Activate on "review my PR / changes / branch", "vet before pushing", "PR review", "is this ready to merge". Fans out parallel sub-agents over skill content, the skill-vs-tool boundary (solution hierarchy), tool correctness…
winui-code-review
Code quality review for WinUI 3 apps — MVVM compliance, x:Bind correctness, accessibility, theming, security, and performance. Use before committing to catch issues that the compiler and UI tests won't find.
verify
Answer "is this shippable / done?" with evidence before a commit or PR — fires on "verify", "is this done", "ready to ship?", pre-commit or pre-PR. Part of the Agentsmith harness; runs the project's verify phases and never claims "passing" without showing the output (R5).
karpathy-guidelines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code. Derived from Andrej Karpathy's LLM coding pitfalls.
verify-readme-features
Verifies that features listed in a README (or similar documentation) are actually implemented in the codebase. Use when user mentions verify features, check feature list, confirm README, validate documentation claims, or audit feature accuracy. Helps catch stale, missing, or inaccurate feature descriptions.
lead-review
Autonomous comprehensive review. Once-through pipeline over /review-health, /review-arch, /review-security, /review-perf, /review-a11y, /review-test, /review-release. Operator-configurable ticket creation at startup — when ON, auto-approves sub-skill ticket proposals per the orchestrator-family contract; when OFF…