Borrowing it
Nothing to install: this file belongs to snowmead/rust-docs-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/snowmead/rust-docs-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/snowmead/rust-docs-mcpWrote 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/instructions/snowmead/rust-docs-mcp/claude-md)<a href="https://agentmods.dev/instructions/snowmead/rust-docs-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/snowmead/rust-docs-mcp/claude-md/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/instructions/snowmead/rust-docs-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/snowmead/rust-docs-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00599 | $0.00599 |
| Opus 5.5 | $0.00240 | $0.00240 |
| Sonnet 5.5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
rust-docs-mcp CLAUDE.md 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 2mo 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.
What it actually says
When testing the rust-docs MCP server, call the tools from the rust-docs-testing MCP.
MCP Rust SDK Macros
Core Macros for Tool Declaration
-
#[tool_router]- Applied to impl blocks to generate tool routing- Automatically creates a
tool_router()method returningToolRouter<Self> - Must be used on the service struct's implementation
- Automatically creates a
-
#[tool]- Marks individual methods as MCP tools- Required parameter:
description = "tool description" - Methods must be
pub async fn - Can return any serializable type
- Required parameter:
-
#[tool_handler]- Applied toServerHandlertrait implementation- Required for the service to work with
serve_server() - Must implement
get_info()returningServerInfo
- Required for the service to work with
Parameter Handling
Parameters<T>Wrapper - Required for ALL tool parameterspub async fn my_tool(&self, Parameters(params): Parameters<MyParams>) -> String- Type
Tmust implementJsonSchema,Deserialize,Serialize - Always destructure with
Parameters(params)pattern
- Type
Required Imports
use rmcp::{
ServerHandler,
handler::server::{router::tool::ToolRouter, tool::Parameters},
model::{ServerCapabilities, ServerInfo},
tool, tool_handler, tool_router,
};
Note: Parameters must be imported from handler::server::tool::Parameters, not directly from rmcp.
Complete Service Pattern
use rmcp::{
ServerHandler,
handler::server::{router::tool::ToolRouter, tool::Parameters},
model::{ServerCapabilities, ServerInfo},
tool, tool_handler, tool_router,
};
use schemars::JsonSchema;
use serde::{Deserialize, Serialize};
#[derive(Debug, Clone, Serialize, Deserialize, JsonSchema)]
pub struct MyParams {
#[schemars(description = "Parameter description")]
pub param_name: String,
}
#[derive(Debug, Clone)]
pub struct MyService {
tool_router: ToolRouter<Self>,
// other fields
}
#[tool_router]
impl MyService {
pub fn new() -> Self {
Self {
tool_router: Self::tool_router(), // Generated by macro
// other fields
}
}
#[tool(description = "Does something useful")]
pub async fn my_tool(&self, Parameters(params): Parameters<MyParams>) -> String {
// Implementation using params.param_name
format!("Processed: {}", params.param_name)
}
}
#[tool_handler]
impl ServerHandler for MyService {
fn get_info(&self) -> ServerInfo {
ServerInfo {
capabilities: ServerCapabilities::builder().enable_tools().build(),
// other config
}
}
}
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.
- 2mo ago First seen · 91 lines · 599 tokens per session scan A 7b2148197a02
rust-docs-mcp CLAUDE.md is an instructions file published in the GitHub repository snowmead/rust-docs-mcp (140 stars, last pushed 1mo ago), licensed MIT. It adds 599 tokens to every session, about $0.0024 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.