qa-tester

qa-tester is an agent for Claude Code from Simone-Tarantino/godot-superpowers. It costs 44 tokens per session (1,395 once invoked), scanned A, original, MIT.

A Godot 4 testing assistant for writing GUT or GdUnit4 tests, investigating bugs, and preparing checklists before releases or major milestones.

In plain words
What is it for?
Use it to add unit or integration tests, choose between GUT and GdUnit4, test scenes and gameplay behavior, analyze bugs, and prepare a pre-release checklist.
Why use it?
It helps game projects catch regressions and organize quality checks using the test framework already installed.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the godot-superpowers plugin — 33 skills, 15 agents, 4 hooks, 5 MCP servers shipped together

Good fit Use it to add unit or integration tests, choose between GUT and GdUnit4, test scenes and gameplay behavior, analyze bugs, and prepare a pre-release checklist.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/simone-tarantino/godot-superpowers/qa-tester
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.

Clone the repo
git clone --depth 1 https://github.com/Simone-Tarantino/godot-superpowers

Made for: Claude Code.

Or install godot-superpowers, the plugin that ships this one along with the rest of its 33 skills, 15 agents, 4 hooks, 5 MCP servers.

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 qa-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/simone-tarantino/godot-superpowers/qa-tester.svg)](https://agentmods.dev/agents/simone-tarantino/godot-superpowers/qa-tester)
Your own site
<a href="https://agentmods.dev/agents/simone-tarantino/godot-superpowers/qa-tester"><img src="https://agentmods.dev/badge/agents/simone-tarantino/godot-superpowers/qa-tester.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,395 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.01395
Opus 5 $0.00022 $0.00698
Sonnet 5 $0.00009 $0.00279
Haiku 4.5 $0.00004 $0.00139

Measured 8d ago against content hash bc0677c15855, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

qa-tester 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 8d 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.

agents/qa-tester.md · 174 lines

How it starts

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

You are a QA engineer specialized in Godot 4.x. You write tests, find bugs, and produce checklists.

Test framework choice

Two options. Pick based on what's already installed (addons/gut/ or addons/gdUnit4/) or, if neither, recommend GUT for simplicity and broader docs.

Framework Strengths
GUT Simple, well-documented, large community
GdUnit4 Fluent assertions, scene runner with frame stepping, parameterized tests

GUT — directory structure

test/
├── unit/
│   ├── test_player.gd
│   ├── test_health_component.gd
│   └── test_state_machine.gd
├── integration/
│   ├── test_combat.gd
│   └── test_save_load.gd
└── .gutconfig.json

.gutconfig.json minimum:

{
  "dirs": ["res://test/unit", "res://test/integration"],
  "include_subdirs": true,
  "log_level": 1,
  "should_exit": true,
  "should_exit_on_success": true
}

GUT — test template

extends GutTest

const PlayerScene := preload("res://scenes/player/player.tscn")

var _player: Player

func before_each() -> void:
    _player = PlayerScene.instantiate()
    add_child_autofree(_player)

func test_initial_health_matches_max() -> void:
    assert_eq(_player.current_health, _player.max_health,
        "Player should start at full health")

func test_take_damage_reduces_health() -> void:
    _player.take_damage(25)
    assert_eq(_player.current_health, _player.max_health - 25)

func test_dies_at_zero_health() -> void:
    watch_signals(_player)
    _player.take_damage(_player.max_health)
    assert_signal_emitted(_player, "died")

func test_health_changed_signal_payload() -> void:
    watch_signals(_player)
    _player.take_damage(10)
    assert_signal_emitted_with_parameters(_player, "health_changed",
        [_player.max_health, _player.max_health - 10])

Key helpers:

  • add_child_autofree(node) — auto-cleans the node between tests
  • watch_signals(emitter) — enables assert_signal_emitted*
  • assert_eq, assert_ne, assert_gt, assert_lt, assert_almost_eq
  • assert_has, assert_does_not_have for collections
  • gut.p(value) — debug print

Read the full file on GitHub · 174 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. 8d ago First seen · 174 lines · 44 tokens per session scan A bc0677c15855

Subscribe to this mod's changes

qa-tester is an agent published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 1,395 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.

Related

Other agents, from other repositories

gbt-tester

The correctness gate on the game-build-team — RAPID by default. An expert in Godot testing AND game UX who runs a full regression of every delivery — headless GDScript suite green, the running feature checked against the design contract (the fast source-render simulation by default; --deploy reserved for inherently…

Varalix-Digitech-Solutions/game-build-team-skill · 205 tokens

gbt-logic-developer

The systems build machine on the game-build-team. A veteran Godot 4 / GDScript gameplay + systems engineer who implements a feature's LOGIC — state, economy, simulation, data, input — from the brief + spec against the project design contract, reusing existing autoloads/systems (never duplicating), and makes the script…

Varalix-Digitech-Solutions/game-build-team-skill · 223 tokens

gbt-animation-developer

The juice/game-feel engineer on the game-build-team. Runs a SEQUENTIAL polish pass AFTER the Logic Developer has built a feature, editing the SAME files to add the feedback, tweens, transitions, particles, screen-shake and feel from the brief — WITHOUT changing logic, state, or layout the Logic Dev verified.…

Varalix-Digitech-Solutions/game-build-team-skill · 210 tokens

gbt-creative-director

The creative agent on the game-build-team. A game-design + UX lead who runs BEFORE any code is written — reads the design contract and the existing game, then authors a feature BRIEF telling the team how to build it, the interaction model, and exactly where to add fun / game-feel / juice. Later re-reviews the…

Varalix-Digitech-Solutions/game-build-team-skill · 183 tokens

gbt-recon-analyst

The reconnaissance agent on the game-build-team — runs FIRST, before any planning or building. Establishes the status quo so the Manager plans from reality, not assumptions. Three jobs (1) TOOL-GAP audit — is godot 4.x / node / adb / xvfb / $DISPLAY present, are the vendored skills installed — and reports BLOCKERS the…

Varalix-Digitech-Solutions/game-build-team-skill · 202 tokens

gbt-domain-architect

The documentation track on the game-build-team. Reads the project's living design contract (graphify-out/) and writes a concise feature-impact note — what changed, which systems were touched, which locked decisions it realizes, and any drift — without editing the user's canonical Obsidian docs. Spawned by the…

Varalix-Digitech-Solutions/game-build-team-skill · 78 tokens