rust-bevy-test-conventions

rust-bevy-test-conventions is a skill for Claude Code, Codex from kimgoetzke/coding-agent-configs. It costs 44 tokens per session (2,151 once invoked), scanned A, original, MIT.

Testing conventions for Bevy, a Rust game-development framework that uses an entity-component-system design. The examples show how to test systems and their state changes with a small running app.

In plain words
What is it for?
Use it when writing tests for Bevy systems, components, resources, plugins, input handling, or game state transitions.
Why use it?
Bevy systems often depend on plugins, resources, entities, and scheduled updates, so isolated function tests may not reflect how the game runs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when writing tests for Bevy systems, components, resources, plugins, input handling, or game state transitions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kimgoetzke/coding-agent-configs/rust-bevy-test-conventions
Install

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.

Any agent
npx skills add kimgoetzke/coding-agent-configs --skill rust-bevy-test-conventions
Clone the repo
git clone --depth 1 https://github.com/kimgoetzke/coding-agent-configs

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for rust-bevy-test-conventions

README.md
[![agentmods](https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/rust-bevy-test-conventions.svg)](https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/rust-bevy-test-conventions)
Your own site
<a href="https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/rust-bevy-test-conventions"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/rust-bevy-test-conventions.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,151 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.02151
Opus 5 $0.00022 $0.01076
Sonnet 5 $0.00009 $0.00430
Haiku 4.5 $0.00004 $0.00215

Measured 7d ago against content hash 51b1a5d6e804, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

rust-bevy-test-conventions 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 7d 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.

skills/rust-bevy-test-conventions/SKILL.md · 381 lines

How it starts

The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rust Bevy test conventions

Quick start

#[cfg(test)]
mod tests {
    use super::*;
    use bevy::prelude::*;
    use bevy::MinimalPlugins;

    fn setup() -> App {
        let mut app = App::new();
        app.add_plugins((MinimalPlugins, YourPlugin));
        app
    }

    #[test]
    fn system_produces_expected_output() {
        let mut app = setup();

        // Setup: Add resources and entities
        app.insert_resource(YourResource::default());

        // Action: Run the system
        app.update();

        // Assert: Verify results
        let resource = app.world().resource::<YourResource>();
        assert_eq!(resource.value, expected_value);
    }
}

Testing ECS systems

Integration-style approach

Test Bevy systems using full App instances with MinimalPlugins:

fn setup() -> App {
    let mut app = App::new();
    app.add_plugins((
        MinimalPlugins,
        YourPlugin,
        // Add other required plugins
    ));
    app
}

#[test]
fn player_input_system_sends_move_message() {
    let mut app = setup();

    // Setup state
    app.insert_resource(NextState::Pending(AppState::Playing));
    app.update(); // Apply state transition

    // Trigger system behavior
    app.world_mut().send_event(KeyboardInput {
        key_code: KeyCode::KeyW,
        state: ButtonState::Pressed,
        /* ... */
    });
    app.update();

    // Verify via message resource
    let messages = app.world().resource::<Messages<MoveMessage>>();
    assert!(!messages.is_empty());
}

Setup helper functions

Create a common setup() function to reduce boilerplate:

fn setup() -> App {
    let mut app = App::new();
    app.add_plugins((MinimalPlugins, ControlsPlugin, StatesPlugin));
    app.init_resource::<Messages<YourMessage>>();
    app
}

fn setup_with_player() -> App {
    let mut app = setup();
    app.world_mut().spawn(Player::default());
    app
}

State simulation

Use NextState to manually advance system states:

Read the full file on GitHub · 381 lines

Changes

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.

  1. 7d ago First seen · 381 lines · 44 tokens per session scan A 51b1a5d6e804

Subscribe to this mod's changes

rust-bevy-test-conventions is a skill published in the GitHub repository kimgoetzke/coding-agent-configs (2 stars, last pushed 18d ago), licensed MIT. It adds 44 tokens to every session and 2,151 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-08-31.