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.
git clone --depth 1 https://github.com/zircote/rust-lspWrote 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/commands/zircote/rust-lsp/setup)<a href="https://agentmods.dev/commands/zircote/rust-lsp/setup"><img src="https://agentmods.dev/badge/commands/zircote/rust-lsp/setup/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/commands/zircote/rust-lsp/setup"><img src="https://agentmods.dev/badge/commands/zircote/rust-lsp/setup.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.00000 | $0.00941 |
| Opus 5.5 | $0.00000 | $0.00376 |
| Sonnet 5.5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
setup 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 1mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust LSP & Toolchain Setup
Set up rust-analyzer LSP integration and install all cargo tools required by the hooks in this project.
Instructions
Execute the following setup steps in order:
1. Verify Rust Toolchain
Check that rustup and cargo are installed:
rustup --version && cargo --version
If not installed, guide the user to https://rustup.rs/
2. Install rust-analyzer
Check if rust-analyzer is available:
which rust-analyzer || rustup component add rust-analyzer
3. Install Nightly Toolchain (required for some tools)
rustup toolchain install nightly
4. Install Required Cargo Tools
Install all tools used by the hooks in hooks/hooks.json:
# Core tools (required)
cargo install cargo-audit # Security vulnerability scanning
cargo install cargo-deny # License and security policy enforcement
cargo install cargo-outdated # Dependency freshness check
# Enhanced analysis (recommended)
cargo install cargo-machete # Unused dependency detection (fast)
cargo install cargo-semver-checks # API compatibility verification
cargo install cargo-geiger # Unsafe code metrics
# Development aids (optional)
cargo install cargo-expand # Macro expansion viewer
cargo install cargo-bloat # Binary size analysis
cargo install cargo-mutants # Mutation testing
# Nightly-only tools
cargo +nightly install cargo-udeps # Unused dependencies (comprehensive)
5. Verify LSP Configuration
Check that .lsp.json exists and is properly configured:
cat .lsp.json
Expected configuration:
{
"rust": {
"command": "rust-analyzer",
"args": [],
"extensionToLanguage": {
".rs": "rust"
},
"transport": "stdio"
}
}
6. Initialize deny.toml (if using cargo-deny)
If this project uses cargo deny, ensure deny.toml exists:
[ -f deny.toml ] || cargo deny init
7. Verify Hooks Configuration
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.
- 1mo ago First seen · 144 lines · 0 tokens per session scan A 8e450d618b83
setup is a command published in the GitHub repository zircote/rust-lsp (13 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 941 tokens. 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 commands, from other repositories
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.
rust-teach
One-time setup that scans your Rust project, understands its patterns and conventions, and writes a Rust-specific context section to your CLAUDE.md. Run once per project to establish persistent Rust guidelines.
rust-harden
Harden Rust code — replace unwrap with proper error handling, add safety comments to unsafe blocks, enable overflow checks, validate inputs at boundaries. The defensive hardening pass.
rust-polish
Final pre-merge polish — remove dead code, verify doc comments, clean clippy, check all Result paths, remove debug artifacts. The last 5% that takes 50% of the effort.
rust-types
Strengthen the type system — replace primitive obsession with newtypes, booleans with enums, stringly-typed APIs with domain types. Make illegal states unrepresentable.
setup
Interactive setup for C/C++ LSP development environment.