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 commands/zircote/rust-lsp/setupgit clone --depth 1 https://github.com/zircote/rust-lspWhat 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.00000 | $0.00941 |
| Opus 5 | $0.00000 | $0.00470 |
| Sonnet 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 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.
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.
- 2d ago First seen · 144 lines · 0 tokens per session scan A 8e450d618b83
setup is a command published in the GitHub repository zircote/rust-lsp (12 stars, last pushed 22d 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
brooks-audit
Run a Brooks-Lint architecture audit.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.