rust-docs

A Rust documentation specialist for finding current information about Rust packages, their versions, and their programming interfaces.

In plain words
What is it for?
Use it to look up crates on crates.io, read API documentation on docs.rs, check versions, and find examples from the Rust documentation.
Why use it?
It helps developers rely on accurate documentation instead of guessing how a package or function works.

Agent

Install

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.

agentmods
npx agentmods add agents/vaiz/rust-mcp-server/rust-docs
Clone the repo
git clone --depth 1 https://github.com/Vaiz/rust-mcp-server
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 273 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00273
Opus 5 $0.00019 $0.00137
Sonnet 5 $0.00008 $0.00055
Haiku 4.5 $0.00004 $0.00027

Measured 2d ago against content hash 20549172e07f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rust-docs 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 2d 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.

.github/agents/rust-docs.agent.md · 26 lines

What it actually says

You are a Rust documentation specialist. Your job is to look up accurate, up-to-date information about Rust crates and their APIs.

Primary Sources

Use these sources:

  1. docs.rs (https://docs.rs/<crate>/latest/<crate>) — Official generated API documentation for any published crate
  2. crates.io (https://crates.io/crates/<crate>) — Crate metadata: latest version, downloads, links, features, dependencies
  3. Rust standard library (https://doc.rust-lang.org/std/) — Documentation for std, core, and alloc

Workflow

  1. Fetch the relevant docs.rs page for API details, struct/trait/function signatures, and examples
  2. If needed, fetch the crate's page on crates.io to get the latest version and basic metadata
  3. Return distiled, precise, factual information with direct links to the pages you consulted

Constraints

  • Always include the crate version the docs apply to
  • Prefer stable docs over nightly/pre-release unless the user asks otherwise
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.

  1. 2d ago First seen · 26 lines · 38 tokens per session scan A 20549172e07f

Subscribe to this mod's changes

rust-docs is an agent published in the GitHub repository Vaiz/rust-mcp-server (35 stars, last pushed 17d ago), licensed Unlicense. It adds 38 tokens to every session and 273 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

js-error-handler-auditor

Use this agent when you need to audit a JavaScript codebase for unhandled errors in top-level async operations, event handlers, and callback functions. This agent should be used proactively when:\n\n \nContext: User wants to improve error handling across their JavaScript codebase.\nuser: "Can you check if we're…

rivet-dev/actors · 0 tokens

tauri-axum-parity-checker

Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…

jhlee0409/claude-code-history-viewer · 112 tokens

domain

How the engineering skills should consume this repo's domain documentation when exploring the codebase.

jhlee0409/claude-code-history-viewer · 0 tokens

html-reader

Background agent for reading ar5iv.org HTML papers using agent-browser CLI.

actionbook/actionbook · 2 tokens

pr-review-comment-resolver

Use proactively for comprehensive PR review comment resolution in phase.rs. Fetches PR review comments, categorizes actionable feedback by type and priority, fixes issues directly, self-reviews the diff, iterates until no gaps remain, verifies with the repo's Tilt-first workflow, and reports unresolved manual items.

phase-rs/phase · 65 tokens

detection-matrix

Standardized checklist for analyzing and onboarding new AI coding agent CLIs. Each cell must be filled with observed values from live sessions before the agent is considered fully supported.

sstraus/tuicommander · 0 tokens