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/plugins/zircote/rust-lsp/rust-lsp)<a href="https://agentmods.dev/plugins/zircote/rust-lsp/rust-lsp"><img src="https://agentmods.dev/badge/plugins/zircote/rust-lsp/rust-lsp/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/plugins/zircote/rust-lsp/rust-lsp"><img src="https://agentmods.dev/badge/plugins/zircote/rust-lsp/rust-lsp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rust-lsp 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.
What it actually says
{
"name": "rust-lsp",
"version": "0.1.8",
"description": "Rust language server",
"author": {
"name": "zircote",
"email": "[email protected]"
},
"repository": "https://github.com/zircote/rust-lsp",
"license": "MIT",
"keywords": [
"rust",
"lsp",
"language-server",
"claude-plugin",
"code-assistant"
]
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 0 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 19 lines scan A a6013c77c934
rust-lsp is a plugin published in the GitHub repository zircote/rust-lsp (13 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-ultra-quality-enforcement marketplace
Ultra-strict quality enforcement plugin with zero-tolerance for errors, warnings, and technical debt. Comprehensive Rust, Python, and TypeScript support with 30+ specialized agents.
dev-workflows-frontend
Skills + Subagents for React/TypeScript - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents.
fuse-rust
Expert Rust 1.98+ (2024 edition) — ownership, error handling, async/tokio, axum backends, cargo tooling, with SOLID principles.
fuse-security
Security vulnerability detection and remediation: OWASP Top 10, SAST scanning, CVE research, dependency audit, secrets detection.
rust-dev
Rust development skill with strict coding standards, FAIL FAST error handling, and implementation/review agents.
rust
Rust code critique, architecture guidance, and idiomatic pattern enforcement.