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/napalmpapalam/skillsWrote 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/napalmpapalam/skills/rust)<a href="https://agentmods.dev/plugins/napalmpapalam/skills/rust"><img src="https://agentmods.dev/badge/plugins/napalmpapalam/skills/rust/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/napalmpapalam/skills/rust"><img src="https://agentmods.dev/badge/plugins/napalmpapalam/skills/rust.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dd:rust 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": "dd:rust",
"version": "0.1.13",
"description": "Rust conventions and best practices for Claude Code",
"author": {
"name": "Semen Loktionov"
}
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 471 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 Changed b47daee81038
- 1mo ago First seen · 9 lines scan A c029acfa17f3
dd:rust is a plugin published in the GitHub repository napalmpapalam/skills (4 stars, last pushed 9d 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-31.
Other plugins, from other repositories
bevy-plugin
Bevy game engine development - ECS, rendering, game architecture.
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.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.