gba-test

A general integration-test command for games running in a Game Boy Advance emulator. Integration tests check that several parts work together through real game actions.

In plain words
What is it for?
Use it for smoke, gameplay, save, stress, full, AI, battle, navigation, or custom test modes supported by the selected game profile.
Why use it?
It adds game detection, documented action recipes, state checks, screenshots, and failure rules to make emulator tests repeatable.

Command

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.

agentmods
npx agentmods add commands/intellegix/intellegix-code-agent-toolkit/gba-test
Clone the repo
git clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 959 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00959
Opus 5 $0.00000 $0.00479
Sonnet 5 $0.00000 $0.00192
Haiku 4.5 $0.00000 $0.00096

Measured 2d ago against content hash 73f7ac202adc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gba-test 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 2d 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.

commands/gba-test.md · 87 lines

How it starts

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

/gba-test — Universal GBA Integration Test Runner

$ARGUMENTS: test mode — game profile defines available modes (e.g., smoke, gameplay, save, stress, full, ai, battle, nav, custom <description>)

5 ABSOLUTE RULES (NEVER VIOLATE)

  1. VERIFY state before every action (screenshot + frame check)
  2. Use ONLY named RECIPES from the game's guide — never invent button sequences
  3. Frame advances >30 require a state check before next action
  4. Screenshot every 5 tool calls
  5. If assertion fails → STOP, report failure + actual state, never retry blindly

Step 1: Detect Game

  1. gba_get_frame — if fails, stop and report "emulator not connected"
  2. Read ROM title: gba_read_memory(0x080000A0, 12) — decode as ASCII
  3. Match title against known profiles:
ROM Title Contains Profile
POKEMON EMER or POKEMON FIRE profiles/pokemon-embergold.md
BRAINATTIC profiles/brain-attic.md
  1. If no match: run Generic Boot Test only (see below), then stop

Step 2: Load Profile

  1. Read the matched profile file from ~/.claude/commands/profiles/
  2. Read the game's guide file (path specified in profile) completely — MANDATORY before any further MCP calls
  3. Note the profile's available test modes and recipes

Step 2.5: Johto Mode Prerequisites

If the requested mode starts with johto-:

  1. Check which save state slots exist by attempting gba_load_state(N) for slots 2-8:
    • If slot loads without error and pokemon_get_map returns group=43 → slot is valid Johto checkpoint
    • Track which slots are available vs missing
  2. Report available vs required slots
  3. If zero Johto save states exist (none of slots 2-8 are valid), STOP and report:
    Johto test modes require save states at story checkpoints.
    Play through the game and save at each checkpoint per the guide (section 9).
    Required slots: 2 (New Bark) through 8 (Blackthorn City).
    
  4. If some slots exist, proceed with available checkpoints only. Report which phases will be skipped due to missing slots.
  5. Reload a known-good state before continuing: gba_load_state(1) to restore Kanto baseline.

Read the full file on GitHub · 87 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. 2d ago First seen · 87 lines · 0 tokens per session scan A 73f7ac202adc

Subscribe to this mod's changes

gba-test is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 959 tokens. 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.