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/sailingnaturali/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/sailingnaturali/claude-skills/signalk-wasm)<a href="https://agentmods.dev/plugins/sailingnaturali/claude-skills/signalk-wasm"><img src="https://agentmods.dev/badge/plugins/sailingnaturali/claude-skills/signalk-wasm/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/sailingnaturali/claude-skills/signalk-wasm"><img src="https://agentmods.dev/badge/plugins/sailingnaturali/claude-skills/signalk-wasm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
signalk-wasm 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 today.
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": "signalk-wasm",
"description": "WebAssembly in SignalK: sandboxed WASM plugins (Rust/AssemblyScript ABI, capabilities, endpoints, providers, verified runtime bugs) and wasm-pack libraries inside Node plugins.",
"version": "0.1.0",
"author": { "name": "Dirk Wahrheit" },
"license": "MIT",
"keywords": ["signalk", "marine", "wasm", "webassembly", "rust", "plugin"]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 226 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.
- today First seen · 9 lines scan A ed7bfa325f0c
signalk-wasm is a plugin published in the GitHub repository sailingnaturali/claude-skills (3 stars, last pushed yesterday), 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-10-19.
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.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.