agentmods.dev

test

A test-stage coordinator for Symfony API changes that checks implementation against a planned test matrix.

In plain words
What is it for?
Use it to run API tests, find and kill escaped Infection mutants, audit new tests, and write the required API test report.
Why use it?
It verifies acceptance criteria with tests and mutation testing, where code changes are deliberately altered to check whether tests catch failures.

Command

2 3mo ago A scan 32 tokens original MIT
View the source file gerard-labs/superpowers-api-platform
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/gerard-labs/superpowers-api-platform/test
Clone the repo
git clone --depth 1 https://github.com/gerard-labs/superpowers-api-platform
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 396 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.00032 $0.00396
Opus 5 $0.00016 $0.00198
Sonnet 5 $0.00006 $0.00079
Haiku 4.5 $0.00003 $0.00040

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

Security

Grade A, and why

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/test.md · 41 lines

What it actually says

You are the Test stage coordinator. Inputs:

  • .claude/last-api-plan.md — the architecture plan (with test matrix)
  • .claude/last-api-dev-report.md — the dev implementation report (lists classes touched)

Step 1 — Read state files

Read .claude/last-api-plan.md          # extract test matrix
Read .claude/last-api-dev-report.md    # identify critical classes touched

Step 2 — Invoke symfony-tdd-coach via Task

The tdd-coach MUST follow the gold-standard workflow:

  1. Read state files first (architects test matrix is the contract)
  2. Run ./vendor/bin/phpunit --filter=Api → iterate until green
  3. Run ./vendor/bin/infection --filter=<critical-classes> → identify escaped mutants on critical paths
  4. For each killable escapee: Write the killing test (force the invariant), re-run mutation
  5. Emit checklist AC → test path → status covering THE WHOLE matrix
  6. Anti-tautology audit on new tests
  7. Emit report between ===API-TEST-BEGIN=== / ===API-TEST-END===

No "recommend follow-up" on critical paths — kill or reject (the dev report is bounced back).

Step 3 — Persist state file

Write .claude/last-api-test-report.md with the full content between ===API-TEST-BEGIN=== and ===API-TEST-END=== (exclude markers themselves).

Surface to the user:

Tests done. Run /review next.
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 · 41 lines · 32 tokens per session scan A c03c70bacb95

Subscribe to this mod's changes

test is a command published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 396 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.

Backend and APIsPlanningTestingapiapi-platformclaudeclaude-codeclaude-code-pluginsymfony
Related

Other commands, from other repositories

sonicjs-pr-fixer

You are a specialized agent that helps fix and merge problematic PRs in the SonicJS repository. This includes PRs from forks that need cherry-picking, Dependabot PRs that need e2e tests enabled, and any PR that needs fixes before merging.

SonicJs-Org/sonicjs · 0 tokens

sonicjs-seo-blog

Generate a high-quality, SEO-optimized blog post for SonicJS on the topic: $ARGUMENTS.

SonicJs-Org/sonicjs · 0 tokens

create-pr

Create a pull request following the official template.

rootstrap/rails_api_base · 0 tokens

templates

Manage locally-stored email templates for composing messages with variable substitution.

nylas/cli · 0 tokens

run-tests

Run unit and integration tests with proper configuration.

nylas/cli · 11 tokens

symfony-cache

Implement caching strategies using Symfony Cache component.

dev-toolings/superpowers-symfony · 7 tokens