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/PabloLION/bmad-pluginWrote 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/agents/pablolion/bmad-plugin/gds-agent-game-qa)<a href="https://agentmods.dev/agents/pablolion/bmad-plugin/gds-agent-game-qa"><img src="https://agentmods.dev/badge/agents/pablolion/bmad-plugin/gds-agent-game-qa/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/agents/pablolion/bmad-plugin/gds-agent-game-qa"><img src="https://agentmods.dev/badge/agents/pablolion/bmad-plugin/gds-agent-game-qa.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.00875 |
| Opus 5.5 | $0.00016 | $0.00350 |
| Sonnet 5.5 | $0.00008 | $0.00175 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
gds-agent-game-qa 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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 70 lines · 39 tokens per session scan A 2ccbf1bbfd3d
gds-agent-game-qa is an agent published in the GitHub repository PabloLION/bmad-plugin (14 stars, last pushed 6mo ago), with no licence file. It adds 39 tokens to every session and 875 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
pipeline-builder
Use this agent when generating or updating the acceptance test generator for a project, or when the user asks to "build the pipeline", "generate the test generator", "update the pipeline", "create acceptance test infrastructure", or when the ATDD skill reaches step 3 (pipeline generation). Examples: Context: A spec.md…
spec-guardian
Use this agent when reviewing GWT acceptance test specs for implementation leakage, or when the user asks to "check specs", "review specs", "audit specs", "clean up specs", or "check for leakage". Also invoked by the /spec-check command and as part of the ATDD workflow. Examples: Context: User has written acceptance…
formal-verifier
DAE formal verifier. Checks one target function against one confirmed invariant with TLA+ (interleavings, state machines) or Lean 4 (all-inputs properties), reproduces any counterexample against the real code, and never opens a PR. Dispatched in parallel by /engineer.harden at CP8, one per selected target.
unity-test-verifier
Independently verifies one revision-locked Unity task handoff, protects test integrity, classifies evidence and reproducible failures, and never owns production fixes or task closure.
build-evaluator
Grade completed implementation against task acceptance criteria. Use at close step after a build. Not for: plan review, code quality, style, PR gating.
unity-feature-implementer
Implement one revision-locked Unity task contract in its assigned code lane or checkout, keep production changes inside exact ownership, and produce an evidence-backed verifier handoff without claiming task completion.