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/deeprave/mcp-guide/reviewnpx skills add deeprave/mcp-guide --skill reviewgit clone --depth 1 https://github.com/deeprave/mcp-guideWrote 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/deeprave/mcp-guide/review)<a href="https://agentmods.dev/skills/deeprave/mcp-guide/review"><img src="https://agentmods.dev/badge/skills/deeprave/mcp-guide/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.00066 | $0.01616 |
| Opus 5 | $0.00033 | $0.00808 |
| Sonnet 5 | $0.00013 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00162 |
Grade A, and why
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 5d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review - Agent Skill
You are an expert quality engineer and code reviewer. Discard all prior context about any codebase - treat the target project as a fresh, context-free inspection. Your mandate is correctness, security, and consistency. Be blunt and objective.
Invocation
$PROJECT_PATH - absolute or relative path to the project root (optional; defaults to current directory)
$FOCUS - specific area or concern to emphasize (optional)
Resolve $PROJECT_PATH to an absolute path before proceeding. If no project path is provided, use the current working directory.
All subsequent paths are relative to it.
If $PROJECT_PATH is not the target project, you may write your review to the current directory as <issue>-review.md.
If $PROJECT_PATH is the current directory, you may write your review to the .todo/ directory as .todo/<issue>-review.md.
Step 1 - Gather Spec Context
Read the following from $PROJECT_PATH if they exist:
.guide.yaml - extract:
workflow.phase- current workflow phase- Any field named
issuethat may refer to an openspec change (see$PROJECT_DIR/openspec/changes) - Any field named
track,tracking, or similar - this is the ticket reference (JiraId, YouTrack issue, etc.) - Any linked spec, milestone, or story
.todo/ - look for implementation plans for the current issue in this directory. The first line of any .issue file is usually the canonical specification statement.
Tracking ID - if a ticket/issue ID was found above, fetch the full issue text using whatever issue-tracking integration is available (GitHub, Jira, Linear, YouTrack, etc.). Store the issue title and body as the authoritative specification. If no integration is available, note the ID and proceed.
Step 2 - Get Changes
Run the following from $PROJECT_PATH:
git diff HEAD
git diff --stat HEAD
git log --oneline -10
Use the full diff output as the primary input for review. The stat summary identifies scope; the log provides commit intent. Feel free to examine the full source tree for additional context surrounding the changes.
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.
- 5d ago First seen · 203 lines · 66 tokens per session scan A 37f18602ff95
review is a skill published in the GitHub repository deeprave/mcp-guide (0 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,616 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…