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/geoffjay/claude-pluginsWrote 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/geoffjay/claude-plugins/rust-cli-developer)<a href="https://agentmods.dev/plugins/geoffjay/claude-plugins/rust-cli-developer"><img src="https://agentmods.dev/badge/plugins/geoffjay/claude-plugins/rust-cli-developer/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/geoffjay/claude-plugins/rust-cli-developer"><img src="https://agentmods.dev/badge/plugins/geoffjay/claude-plugins/rust-cli-developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rust-cli-developer 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-cli-developer",
"source": "./plugins/rust-cli-developer",
"description": "Experienced Rust developer with expertise in building delightful CLI applications using Clap and the Rust CLI ecosystem",
"version": "1.0.0",
"author": {
"name": "Geoff Johnson",
"url": "https://github.com/geoffjay"
},
"homepage": "https://github.com/geoffjay/claude-plugins",
"repository": "https://github.com/geoffjay/claude-plugins",
"license": "MIT",
"keywords": [
"rust",
"cli",
"clap",
"command-line",
"terminal",
"tui",
"ux",
"testing"
],
"category": "languages",
"strict": false,
"agents": [
"./agents/clap-expert.md",
"./agents/cli-ux-specialist.md",
"./agents/cli-architect.md",
"./agents/cli-testing-expert.md"
],
"commands": [
"./commands/cli-scaffold.md",
"./commands/cli-review.md",
"./commands/cli-test.md",
"./commands/cli-enhance.md"
],
"skills": [
"./skills/clap-patterns",
"./skills/cli-ux-patterns",
"./skills/cli-configuration",
"./skills/cli-distribution"
]
}What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 126 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#rust-cli-developer in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 43 lines scan A 1822a8ecdc22
rust-cli-developer is a plugin published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 11mo 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-09-03.
Other plugins, from other repositories
bevy-plugin
Bevy game engine development - ECS, rendering, game architecture.
dd:rust
Rust conventions and best practices for Claude Code.
rust-tools
SOTA Rust tooling - refactoring, profiling, benchmarking, testing, SIMD, dependency audit.
systemprompt-dev
Complete development toolkit: Rust, frontend, architecture standards, extension development guides, and 6 specialized agents.
askama
Askama Rust template engine guidance with anti-rationalization patterns for scope errors and Jinja2 migration.
rust-developer
Comprehensive Rust development assistance for building, testing, and deploying Rust applications with cargo, clippy, async patterns, and framework support.