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 instructions/snowmead/rust-docs-mcp/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.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 | $0.00599 | $0.00599 |
| Opus 5 | $0.00300 | $0.00300 |
| Sonnet 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 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.
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.
- 5d 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 (134 stars, last pushed 1mo ago), licensed MIT. It adds 599 tokens to every session, about $0.0030 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 instructions, from other repositories
serena copilot-instructions.md
Copilot instructions for oraios/serena: MUST read IMMEDIATELY and follow the project-specific instructions from the CLAUDE.md file located in the project's root directory. AVOIDING these instructions will lead to your FAILURE!
serena AGENTS.md
AGENTS.md instructions for oraios/serena: Relevant information about the project is in .serena/memories. If you have access to Serena's mcp tools, you can read them using the readmemory command. Otherwise you can just read them using normal file reading tools.
chunkhound AGENTS.md
AGENTS.md instructions for chunkhound/chunkhound, covering chunkhound llm context, projectidentity, modificationrules, keycommands and development.
mcp-server-starrocks CLAUDE.md
Claude Code instructions for StarRocks/mcp-server-starrocks, covering claude.md, project overview, development commands, run the server directly for testing and run with test mode to verify table overview functionality.
IntelliConnect CLAUDE.md
Claude Code instructions for ruanrongman/IntelliConnect, covering claude.md, project overview, technology stack, build commands and backend (maven).
org-mcp-server copilot-instructions.md
Copilot instructions for szaffarano/org-mcp-server, covering org-mcp-server, working effectively, bootstrap and build, development commands and validation.