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.
npx agentmods add plugins/rune-kit/rune/rune/plugin marketplace add Rune-kit/runegit clone --depth 1 https://github.com/Rune-kit/runeGrade A, and why
rune 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": "rune",
"version": "2.32.0",
"description": "67-skill mesh for Claude Code with runtime auto-discipline — native hooks (preflight/sentinel/completion-gate/quarantine) auto-fire at lifecycle boundaries. 248 mesh connections + 46 signals, adaptive routing, mesh analytics, MCP quarantine guidance, and project memory.",
"author": {
"name": "Rune Contributors"
},
"repository": "https://github.com/rune-kit/rune",
"homepage": "https://rune-kit.github.io/rune",
"license": "MIT",
"keywords": ["skills", "mesh", "tdd", "multi-platform", "coding-agent"],
"premium": {
"pro": {
"name": "Rune Pro",
"price": "$49 lifetime",
"packs": ["product", "sales", "data-science", "support", "growth", "media", "personal-brand", "ecommerce", "vietnam"],
"url": "https://rune-kit.github.io/rune#pricing"
},
"business": {
"name": "Rune Business",
"price": "$149 lifetime",
"packs": ["finance", "legal", "hr", "enterprise-search"],
"includes": "pro",
"url": "https://rune-kit.github.io/rune#pricing"
}
}
}
What ships with it
1 file beside plugin.json 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 First seen · 28 lines scan A 744aaea969ab
rune is a plugin published in the GitHub repository Rune-kit/rune (84 stars, last pushed 16d 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-30.
Other plugins, from other repositories
paperthin
Low-level agentic design patterns. Turning old engineering wisdom into reflexes your agent reaches for on its own—on any agent.
jaiskills
Orchestration (insistir, constatar, remoto), prompting (metaprompt), knowledge compounding, file-based TODOs, and OpenAI tooling (askcodex, image-to-frontend) as one Claude Code plugin.
jaiskills
Jairo's agent skills for Claude Code — orchestration, verification, prompting, and OpenAI tooling in one plugin.
missing-codex-manifest
Anti fixture: declares claude+codex agent-targets but ships no .codex-plugin manifest, to trip S6.
agent-skills
Plugin marketplace listing 1 plugin: agent-skills.
claude-wave-plugin
Wave-based engineering execution for Claude Code. Vendors the full v2 framework — 17-phase pipeline plus conditional [DR] (UI waves) and [CR] (opt-in) gates, model-routed across Opus/Sonnet/Haiku, hook-enforced invariants, worktree isolation — plus a polished 5-phase demo subset for live segments and small UI features.