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-integration-to-unit-migratingnpx skills add shopwareLabs/ai-coding-tools --skill phpunit-integration-to-unit-migratinggit 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-integration-to-unit-migrating)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/phpunit-integration-to-unit-migrating"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/phpunit-integration-to-unit-migrating.svg" alt="Measured on agentmods" 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 | $0.00152 | $0.02734 |
| Opus 5 | $0.00076 | $0.01367 |
| Sonnet 5 | $0.00030 | $0.00547 |
| Haiku 4.5 | $0.00015 | $0.00273 |
Grade A, and why
phpunit-integration-to-unit-migrating 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHPUnit Integration-to-Unit Migration
Audits integration tests for misplacement and migrates the ones whose apparatus is not load-bearing.
When to use
- User explicitly asks to audit integration tests for migration candidates
- User points at a file/directory/PR and asks "should these be unit tests?"
- Following the placement smoke-alarm hint from
phpunit-integration-test-reviewing
This skill is adversarial about placement. It assumes integration tests are misplaced until proven otherwise. Do not invoke for general integration test review — use phpunit-integration-test-reviewing for that.
Workflow
digraph migration_audit {
"User invocation" [shape=doublecircle];
"Resolve scope" [shape=box];
"Per test: articulate SUT contract" [shape=box];
"Walk PLACEMENT-001..008" [shape=box];
"Veto from PLACEMENT-008?" [shape=diamond];
"Bucket: migrate" [shape=box];
"Bucket: split" [shape=box];
"Bucket: keep" [shape=box];
"Bucket: delete (duplicate)" [shape=box];
"Present buckets to user" [shape=box];
"User confirms migration set?" [shape=diamond];
"Execute migrations" [shape=box];
"Report" [shape=doublecircle];
"Stop (user declined)" [shape=octagon, style=filled, fillcolor=red];
"User invocation" -> "Resolve scope";
"Resolve scope" -> "Per test: articulate SUT contract";
"Per test: articulate SUT contract" -> "Walk PLACEMENT-001..008";
"Walk PLACEMENT-001..008" -> "Veto from PLACEMENT-008?";
"Veto from PLACEMENT-008?" -> "Bucket: keep" [label="yes (any veto)"];
"Veto from PLACEMENT-008?" -> "Bucket: migrate" [label="no, all unit-shape"];
"Veto from PLACEMENT-008?" -> "Bucket: split" [label="no, mixed"];
"Veto from PLACEMENT-008?" -> "Bucket: delete (duplicate)" [label="duplicate of unit coverage"];
"Bucket: migrate" -> "Present buckets to user";
"Bucket: split" -> "Present buckets to user";
"Bucket: keep" -> "Present buckets to user";
"Bucket: delete (duplicate)" -> "Present buckets to user";
"Present buckets to user" -> "User confirms migration set?";
"User confirms migration set?" -> "Execute migrations" [label="yes"];
"User confirms migration set?" -> "Stop (user declined)" [label="no"];
"Execute migrations" -> "Report";
}
What ships with it
2 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.
- 2d ago Changed 3758327ba984
- 5d ago First seen · 192 lines · 152 tokens per session scan A ace6640f54dd
phpunit-integration-to-unit-migrating is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (43 stars, last pushed yesterday), licensed MIT. It adds 152 tokens to every session and 2,734 once invoked, about $0.0008 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
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.
configure-memory-profiling
Memory profiling with pytest-memray for Python. Use when setting up memory profiling, adding CI memory regression detection, or setting memory thresholds.
plan
Produce structured implementation plans with goal, approach, test strategy, blast-radius assessment, parallelism analysis, and a user approval gate before any code is written. Persisting PLAN.md for fresh-session handoff. Use when: 'plan this', 'architect this', 'how should we implement', 'implementation plan', 'write…