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 skills/metaspartan/cybara/bevynpx skills add metaspartan/cybara --skill bevygit clone --depth 1 https://github.com/metaspartan/cybaraWrote 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/skills/metaspartan/cybara/bevy)<a href="https://agentmods.dev/skills/metaspartan/cybara/bevy"><img src="https://agentmods.dev/badge/skills/metaspartan/cybara/bevy.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00043 | $0.00403 |
| Opus 5 | $0.00022 | $0.00201 |
| Sonnet 5 | $0.00009 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
bevy 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
Bevy
Inspect first
- Read the workspace
Cargo.toml, lockfile, Bevy version, feature flags, profiles, and target configuration. - Inspect plugins, states, schedules, systems, components, resources, events, assets, examples, and tests near the behavior.
- Identify fixed-timestep, startup, update, rendering, and extraction boundaries.
- Reuse the repository's configured Rust toolchain and task commands.
Implementation rules
- Keep systems focused and make ordering or ambiguity explicit.
- Use events, resources, states, and components according to data ownership rather than as global shortcuts.
- Avoid conflicting mutable queries and broad world access when narrower system parameters work.
- Keep deterministic simulation separate from frame-rate-dependent presentation.
- Preserve asset handles and loading states; do not block the main schedule on synchronous asset work.
- Do not change Bevy versions or default features as part of an unrelated fix.
Verification
- Format with the configured Rust formatter.
- Run focused tests, then workspace tests.
- Run the repository's lint configuration without weakening it.
- Build the affected examples, binaries, and target profiles.
- Launch the game and exercise the changed state transitions and player inputs.
- Inspect panic output, asset diagnostics, schedule ambiguity, render warnings, and platform errors.
Performance
Measure schedule time, system parallelism, entity churn, asset memory, render extraction, draw calls, and frame pacing in representative gameplay. Prefer fewer structural changes and reusable buffers in hot systems, then confirm the result with the same capture.
Completion criteria
Report Bevy and Rust versions, features and target built, tests and lints run, gameplay flow exercised, and any GPU or platform limitation.
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 · 40 lines · 43 tokens per session scan A 0f451e5bf260
bevy is a skill published in the GitHub repository metaspartan/cybara (26 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 403 once invoked, about $0.0002 per session on Opus 5. 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-03.
Other skills, from other repositories
rust-engineer
Acquire expert Rust developer specialisation in rust systems programming, memory safety, and zero-cost abstractions. Masters ownership patterns, async programming, and performance optimisation for mission-critical applications.
loom-rust
Rust language expertise for idiomatic, production-quality code.
rust-development
You MUST activate this skill when working on Rust projects.
vigilante-issue-implementation-on-rust
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Rust repository with Cargo, Clippy, fmt, and security guidance.
tauri2-react-rust
Guides development of cross-platform desktop apps with Tauri 2, TypeScript, React, and Rust. Use when building Tauri apps, implementing IPC, designing Rust backend or TypeScript/React frontend, when researching or cloning a website (open site, snapshot elements), when verifying local dev or built frontend in browser…
ecc-api-patterns
Skill "ecc-api-patterns" from KornLabs/truss, covering fastapi patterns, project structure, app factory and lifespan, app/main.py and configuration with pydantic-settings.