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/terrylica/cc-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/terrylica/cc-skills/rust-tools)<a href="https://agentmods.dev/plugins/terrylica/cc-skills/rust-tools"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/rust-tools/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/terrylica/cc-skills/rust-tools"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/rust-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rust-tools 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 yesterday.
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-tools",
"description": "SOTA Rust tooling - refactoring, profiling, benchmarking, testing, SIMD, dependency audit",
"version": "34.1.0",
"source": "./plugins/rust-tools",
"category": "development",
"author": {
"name": "terrylica",
"url": "https://github.com/terrylica"
},
"keywords": [
"rust",
"cargo",
"ast-grep",
"divan",
"samply",
"cargo-mutants",
"macerator",
"simd",
"pgo",
"pyo3",
"cargo-semver-checks",
"cargo-nextest",
"cargo-wizard",
"cargo-hack",
"cargo-audit",
"cargo-deny",
"cargo-vet"
],
"strict": false
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 92 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside marketplace.json#rust-tools 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.
- yesterday Changed ab940b6f26e3
- 2d ago Changed a72905d38321
- 3d ago Changed 7306772c765d
- 5d ago Changed 7406668bd66a
- 6d ago Changed 0fe31b96e39d
- 8d ago Changed a0500fdf224f
- 13d ago Changed bc4147ddb2a2
- 14d ago Changed c1adb7425f2e
- 15d ago Changed 5d9ca181294b
- 16d ago First seen · 31 lines scan A 777d9975804d
rust-tools is a plugin published in the GitHub repository terrylica/cc-skills (0 stars, last pushed today), 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-05.
Other plugins, from other repositories
rust-network-module
Adapt Rust networking modules to the target crate with bounded TCP listeners, protocol examples, and executable tests.
migration-validator
Safety verification checklist for C-to-Rust migrations — compilation, unsafe minimization, differential testing.
dev-tooling
Three MCP servers for PHP and JavaScript operations. PHP (php-tooling): PHPStan, ECS, Rector, PHPUnit, PHPUnit coverage gap analysis, Symfony Console. Administration (js-admin-tooling): ESLint, Stylelint, Prettier, Jest, TypeScript, Vite builds. Storefront (js-storefront-tooling): ESLint, Stylelint, Jest, Webpack…
apple-skills
164 Apple platform development skills across 23 categories (iOS, macOS, watchOS, visionOS): code generators, product workflow, App Store/ASO, testing and TDD, design, performance, security, and more. Surfaced as 23 category skills that route to the full library.
swift-testing-pro
Swift Testing framework: @Test, #expect, traits, parameterized tests, XCTest migration.
k8s-sidecar-testing
Project-specific Kubernetes test helpers with bounded commands, accurate failure reporting, and scoped cleanup.