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/vinnie357/claude-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/vinnie357/claude-skills/rig)<a href="https://agentmods.dev/plugins/vinnie357/claude-skills/rig"><img src="https://agentmods.dev/badge/plugins/vinnie357/claude-skills/rig/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/vinnie357/claude-skills/rig"><img src="https://agentmods.dev/badge/plugins/vinnie357/claude-skills/rig.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rig 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 5d 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": "rig",
"version": "0.1.2",
"description": "Rig (rig-core): building multi-provider and hybrid LLM clients in Rust",
"author": {
"name": "vinnie357"
},
"repository": "https://github.com/vinnie357/claude-skills",
"license": "MIT",
"keywords": ["rig", "rig-core", "rust", "llm", "agents", "ollama", "mcp"],
"skills": ["./skills/rig"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 110 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.
- 5d ago First seen · 13 lines scan A a8584b8d387f
rig is a plugin published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed 3d 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-04.
Other plugins, from other repositories
azure-sdk-rust
Azure SDK patterns and best practices for Rust developers covering identity, Key Vault, storage, Cosmos DB, and Event Hubs.
playwright-rs
Procedural reference for writing Rust browser automation with playwright-rs: adding the crate and installing its browsers, object model, the locator!() macro, builder options, auto-wait semantics, and trace capture.
rust-tools
SOTA Rust tooling - refactoring, profiling, benchmarking, testing, SIMD, dependency audit.
bevy-plugin
Bevy game engine development - ECS, rendering, game architecture.
rust
Rust language discipline: ownership, idioms, error handling, concurrency, toolchain, and LSP-powered code intelligence.
poly
Zero-dependency lint & format orchestrator over MCP — one pure-Rust binary wrapping ruff/oxc/taplo/rumdl and more as in-process backends, plus a tree-sitter generic tier for everything else. Exposes lint/format/cache tools with structured JSON output.