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/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/bevy-plugin)<a href="https://agentmods.dev/plugins/laurigates/claude-plugins/bevy-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/bevy-plugin/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/laurigates/claude-plugins/bevy-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/bevy-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bevy-plugin 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 21d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "bevy-plugin",
"version": "1.4.2",
"description": "Bevy game engine development - ECS, rendering, game architecture",
"author": {
"name": "Lauri Gates"
},
"license": "MIT",
"keywords": [
"bevy",
"game-engine",
"ecs",
"rust",
"gamedev"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 85 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.
- 21d ago Changed · +4 lines 0fff6f54c984
- 1mo ago Changed 92ea264ef53d
- 1mo ago First seen · 14 lines scan A 9f71b40dd464
bevy-plugin is a plugin published in the GitHub repository laurigates/claude-plugins (60 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-08-30.
Other plugins, from other repositories
dev-agents
Language-agnostic development agents and skills for Claude Code, with Rust and TypeScript stack profiles: 15 specialist agents (architect, developer, testing, performance, security, reviewer, CI/CD, debugger, critic, SDD, live-tester, tech-writer, researcher, architecture and security analysts) that load per-language…
development
All development skills for systemprompt.io: Rust backend (extensions, CLI binaries, MCP servers), web features, canonical per-language coding standards (Rust, JavaScript, CSS) with mechanical forbidden-construct tables, HTML/asset workflow, print factsheet design, distribution-channel validation, and UX/UI design…
rust-developer
Comprehensive Rust development assistance for building, testing, and deploying Rust applications with cargo, clippy, async patterns, and framework support.
bevy
Authoritative idioms for Bevy 0.20 game projects in Rust. Covers ECS data design (incl. resources-as-components), communication (Event/Message/Observer), plugin organization, scheduling, assets, UI (text, widgets, text input), BSN scenes, rendering (WESL shaders), error handling, testing, performance, and 0.16→0.20…
rust
Rust development tools for Claude Code.
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…