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 pnp/copilot-prompts --skill mcp-server-reviewgit clone --depth 1 https://github.com/pnp/copilot-promptsWrote 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/pnp/copilot-prompts/mcp-server-review)<a href="https://agentmods.dev/skills/pnp/copilot-prompts/mcp-server-review"><img src="https://agentmods.dev/badge/skills/pnp/copilot-prompts/mcp-server-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/pnp/copilot-prompts/mcp-server-review"><img src="https://agentmods.dev/badge/skills/pnp/copilot-prompts/mcp-server-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.00093 | $0.02803 |
| Opus 5 | $0.00046 | $0.01401 |
| Sonnet 5 | $0.00019 | $0.00561 |
| Haiku 4.5 | $0.00009 | $0.00280 |
Grade A, and why
mcp-server-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 10d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review an MCP Server Against the 2026-07-28 Revision
Protocol revision 2026-07-28 is the largest change to the Model Context Protocol since it launched. Server code written before it still compiles, still passes its own tests, and still looks correct in review. It simply speaks a shape that modern clients no longer send.
This skill finds that gap. It reviews an MCP server implementation against the current revision, reports what is obsolete, what is missing, and what is a security requirement rather than a nicety, and it distinguishes between a genuine finding and something it could not determine from the code available.
Before Starting
Critical: Always ask the user for the following information before proceeding:
- Server code - the repository, folder, or files implementing the MCP server
- Target revision - the protocol revision the server intends to implement. Defaults to
2026-07-28if not specified - Transport - Streamable HTTP or stdio. Defaults to Streamable HTTP if not specified, since the header rules below apply only to it
- Backward compatibility requirement - whether the server must still serve clients on
2025-03-26through2025-11-25. Defaults to no
If the user doesn't provide all details upfront, ask for the missing ones before proceeding.
Do not infer the revision from an SDK version number. SDK majors and protocol revisions move independently. Read what the code actually sends and accepts.
Output Structure
Produce a review report with these sections:
- Revision verdict - one line stating which revision the code appears to implement, and the evidence for that conclusion
- Blocking findings - table of
Finding | Location | Why it breaks | Fix - Security findings - the spec's security requirements with their MUST or SHOULD levels, listed separately because they are not stylistic
- Deprecated but working - features on the twelve month removal clock
- Not determined - checks that could not be evaluated from the code provided, and what to look at to resolve each
- Nothing to change - the checks that passed
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 180 lines · 93 tokens per session scan A 2f7e4fc7cfe4
mcp-server-review is a skill published in the GitHub repository pnp/copilot-prompts (875 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 2,803 once invoked, about $0.0005 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
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Reviews code for bugs, security issues, and best practices.
audit
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. With…
analyze
Deep-analyzes the current codebase to discover stack, architecture, patterns, conventions, and pitfalls. Creates curated documentation in .vibeflow/ that persists and can be committed to git. Supports incremental updates, scoped deep-dives, interactive review, and satellite repo analysis. Use when setting up a…
enforcement-audit
Run a compliance audit against a technology instruction file, detecting discrepancies, planning workstreams, implementing fixes, and validating quality gates.
spec-to-code-compliance
Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that no document mentions. Use when comparing an implementation against a whitepaper, protocol spec, or design document.