What is mcp-reviewer?

A documentation review workflow for Rust crates, which are reusable Rust software packages, using docs.rs tools. It saves the tools’ exact results as structured files under a crate-specific review folder.

Use it to run crate and symbol searches and document the returned evidence in find, lookup, docs, and symbols review artifacts.

It provides a recorded trail of package searches, documentation lookups, and symbol checks without requiring the reviewer to read the source code.

How vexxvakan/mcp-docsrs configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to vexxvakan/mcp-docsrs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/vexxvakan/mcp-docsrs/main/.agents/skills/mcp-reviewer/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/vexxvakan/mcp-docsrs

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vexxvakan/mcp-docsrs/mcp-reviewer/github.svg)](https://agentmods.dev/skills/vexxvakan/mcp-docsrs/mcp-reviewer)

Your own site

<a href="https://agentmods.dev/skills/vexxvakan/mcp-docsrs/mcp-reviewer"><img src="https://agentmods.dev/badge/skills/vexxvakan/mcp-docsrs/mcp-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vexxvakan/mcp-docsrs/mcp-reviewer"><img src="https://agentmods.dev/badge/skills/vexxvakan/mcp-docsrs/mcp-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 499 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00029	$0.00499
Opus 5	$0.00015	$0.00249
Sonnet 5	$0.00006	$0.00100
Haiku 4.5	$0.00003	$0.00050

Measured 12d ago against content hash 251e58f692c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

mcp-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 12d 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.

.agents/skills/mcp-reviewer/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Reviewer

Do not read the code, just run the available MCP tools.

Workflow

Follow the review flow in order and complete one artifact before starting the next:

Write review/CRATE_NAME/find.md.
Write review/CRATE_NAME/lookup.md.
Write review/CRATE_NAME/docs.md.
Create review/CRATE_NAME/symbols/.

Use the active docsrs MCP tools directly:

crate_find
crate_lookup
crate_docs
symbol_lookup
symbol_docs

Artifact Rules

Capture verbatim tool evidence only.

Record the exact tool name used.
Record the exact parameters passed.
Record the exact markdown/text response from the tool output text field.
Record the exact structured content response from the tool output structuredContent field.
Format the received structured tool output JSON into a Markdown table below the direct tool output.
Preserve failures verbatim; they are valid review evidence.
Rewrite affected files completely if the review scope changes.

Per-File Requirements

For find.md:

Run crate_find 5 times.
Vary parameters across the 5 runs.
Show parameters and the exact returned text for each run.

For lookup.md:

Run crate_lookup 5 times.
Vary parameters across the 5 runs.
Show parameters and the exact returned text for each run.

For docs.md:

Run crate_docs once.
Store the full returned documentation.
Do not trim or summarize the docs output.

For symbols/**.md:

Extract every available symbol from the crate_lookup result.
Run symbol_lookup for every listed symbol.
Run symbol_docs for every listed symbol.
Use the kind and symbol name exactly as exposed by the crate overview.
Show parameters and the exact returned text for every symbol lookup.

Execution Notes

Prefer sequential execution over mixing review phases.
If a crate overview is incomplete or returns no symbols, record that outcome instead of inventing symbol probes.
If the tool response includes markdown fences, preserve them safely in the review artifact by changing the outer fence style when needed.

Read the full file on GitHub · 71 lines

Files

What ships with it

1 file 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.

agents/openai.yaml 276 B

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.

12d ago First seen · 71 lines · 29 tokens per session scan A 251e58f692c2

Subscribe to this mod's changes

mcp-reviewer is a skill published in the GitHub repository vexxvakan/mcp-docsrs (13 stars, last pushed 5d ago), licensed Apache-2.0. It adds 29 tokens to every session and 499 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-30.

Code review Languages Rust

architecture-audit

Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…

org2AI/ORG2 · 70 tokens

rust-review

A Rust code-review skill for services, checking for crashes, unsafe SQL construction, exposed credentials, ignored errors, and unfinished code.

liuyanghejerry/Clausura · 25 tokens

rust-skills

Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros…

leonardomso/rust-skills · 84 tokens

writing-rust

Idiomatic Rust development. Use when writing Rust code, Cargo crates/workspaces, Rust tests, or rustfmt/clippy/cargo workflows. Emphasizes ownership, Result errors, small APIs, stdlib-first dependencies, fast cargo feedback, and behavior tests. NOT for Go, Python, TypeScript, shell scripts, or infra-only work.

alexei-led/cc-thingz · 73 tokens

adversarial-rust

Use this skill when reviewing or refactoring existing Rust code that carries an alien mental model — OO/enterprise ceremony from Java/C#, garbage-collected object graphs, exception-style control flow, or imperative loops ported onto the borrow checker. It is the adversarial, architecture-level counterpart to…

pproenca/dot-skills · 223 tokens

m15-anti-pattern

Use when reviewing code for anti-patterns. Keywords: anti-pattern, common mistake, pitfall, code smell, bad practice, code review, is this an anti-pattern, better way to do this, common mistake to avoid, why is this bad, idiomatic way, beginner mistake, fighting borrow checker, clone everywhere, unwrap in production…

moeru-ai/auv · 101 tokens

mcp-docsrs: Skill for Codex