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.
npx skills add shopwareLabs/ai-coding-tools --skill phpunit-migration-test-generationgit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWrote 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/skills/shopwarelabs/ai-coding-tools/phpunit-migration-test-generation)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/phpunit-migration-test-generation"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/phpunit-migration-test-generation/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/skills/shopwarelabs/ai-coding-tools/phpunit-migration-test-generation"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/phpunit-migration-test-generation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00141 | $0.01397 |
| Opus 5.5 | $0.00056 | $0.00559 |
| Sonnet 5.5 | $0.00028 | $0.00279 |
| Haiku 4.5 | $0.00014 | $0.00140 |
Grade A, and why
phpunit-migration-test-generation 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHPUnit Migration Test Generation
Generate Shopware-compliant PHPUnit migration tests that pass PHPStan and PHPUnit validation.
File Write Restrictions
Write ONLY to:
tests/migration/**— Migration test files
NEVER write to:
src/**— Source code (read-only)tests/unit/**— Unit tests (out of scope)tests/integration/**— Integration tests (out of scope)- Any other directory
Quick Start
- Read the target migration source class
- Analyze SQL operations to determine test pattern
- Apply the migration test template with conditional sections
- Validate with PHPStan and PHPUnit
- Fix any errors and repeat
- Generate completion report
Phase 1: Validate Input
- Verify single file provided
- Verify file exists and is a PHP class (not interface/trait)
- Verify path contains
Migration/V6_ - Verify class extends
Shopware\Core\Framework\Migration\MigrationStep
If validation fails, return FAILED with reason.
Phase 2: Analyze Source
Read the migration class and extract information needed for test generation. See references/source-analysis.md for detection patterns.
Step 1: Extract Metadata
- Class name, full namespace
- Timestamp from
getCreationTimestamp()return value #[Package('...')]attribute value — the test class carries the same value. When the migration class carries none, take the value from the nearestsrc/directory the test path mirrors, walking up until one exists and using the value its.phpfiles carry. When that yields no value, emit no#[Package]and report that in the Phase 5 report'sPackagefield (none, per references/output-format.md) rather than guessing a value.- Area from namespace (
Core,Administration,Storefront,Elasticsearch) - Version from namespace (
V6_6,V6_7,V6_8)
Step 2: Classify SQL Operations
Read update() and updateDestructive() method bodies. Classify:
- Schema-add: CREATE TABLE, addColumn(), ALTER TABLE ... ADD
- Schema-remove: DROP TABLE, DROP COLUMN, dropColumnIfExists(), dropTableIfExists()
- Data-update: UPDATE, INSERT, DELETE on non-config tables
- Config: system_config operations
- Mail-template: mail_template operations
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 92edeea30e54
- 1mo ago Changed 3c1a895d3d04
- 1mo ago Changed 752e9c240c1d
- 1mo ago Changed cd72be8a8d4e
- 1mo ago First seen · 169 lines · 141 tokens per session scan A 14c7bc272374
phpunit-migration-test-generation is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 5d ago), licensed MIT. It adds 141 tokens to every session and 1,397 once invoked, about $0.0006 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 skills, from other repositories
generate-file-name-gate
Emit the file-name gate into a consuming repository: a standalone bash checker plus its own test suite, with the casing rule, roots, and exemptions inlined from the resolved docs-naming configuration, and optionally the path-scoped rule file. The emitted pair carries no dependency on this plugin at run time. Refuses…
test-structural-invariants
For data structure validation: test lengths, relationships, constraints that must hold, verify setup is correct.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
verify-solution-properties
For solution checking: independent verification that result is correct, separate from how it was computed.
verify-with-inline-tests
For test co-location: tests in same file as code, run with main, tests as documentation and examples.
moai-clean
Identify and safely remove dead code with test verification.