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 agentmods add skills/shopwarelabs/ai-coding-tools/phpunit-migration-test-generationnpx skills add shopwareLabs/ai-coding-tools --skill phpunit-migration-test-generationgit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWhat 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 | $0.00141 | $0.01397 |
| Opus 5 | $0.00071 | $0.00698 |
| Sonnet 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 today.
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.
- today Changed cd72be8a8d4e
- 2d 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 (42 stars, last pushed yesterday), licensed MIT. It adds 141 tokens to every session and 1,397 once invoked, about $0.0007 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-30.
Other skills, from other repositories
audit-instructions
Audit locally-owned Claude Code instruction surfaces, including CLAUDE.md, .claude/rules, skill bodies, agent definitions, hook instruction text and output styles, for instructions current models no longer need (prior-model workarounds, over-prescriptive scaffolding, stale examples), instructions that misstate Claude…
audit-permission-state
Report the Claude Code permission state actually in effect. Discovers every settings scope (managed policy, user-global, project, local, and the pre-v2.1.211 start-directory copy), merges them into the effective allow/ask/deny set with each rule's source and precedence mechanic named, and classifies which allow rules…
lanes
Start, restart, stop, and check loop lanes as named background Claude Code sessions seeded from canonical prompt files, the scripted replacement for the manual morning refresh (cancel loop, clear, re-paste the canonical prompt) across N lanes on a machine. start/restart first pull the repo and refresh the plugin…
batch-simplify
Batch-run simplification across changed files, or across an entire repository, grouped by ecosystem and dependency order. Use when: 'batch simplify', 'simplify recent changes', 'simplify everything', 'forgot to run simplify', 'catch up on simplify', 'simplify my branch changes', 'simplify the whole repo', 'simplify…
audit-prompting-postures
Audit locally-owned instruction components, including skill bodies, agent definitions, hook instruction text, output styles, CLAUDE.md and rules, for MISSING posture guidance the official prompting guide says their purpose needs: delegation criteria/caps in orchestration components, minimal-scope and anti-test-gaming…
audit-install-state
Read-only audit of a Claude Code INSTALLATION directory, the machine-scope /.claude tree plus /.claude.json. Inventorying every file, separating what the product's own retention sweep already manages from what nothing manages, resolving what each number in a filename actually means before any process-liveness check…