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 hmj1026/dhpk --skill dhpk-library-dual-testsuite-mapgit clone --depth 1 https://github.com/hmj1026/dhpkWrote 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/hmj1026/dhpk/dhpk-library-dual-testsuite-map)<a href="https://agentmods.dev/skills/hmj1026/dhpk/dhpk-library-dual-testsuite-map"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-library-dual-testsuite-map/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/hmj1026/dhpk/dhpk-library-dual-testsuite-map"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-library-dual-testsuite-map.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.00181 | $0.01244 |
| Opus 5 | $0.00090 | $0.00622 |
| Sonnet 5 | $0.00036 | $0.00249 |
| Haiku 4.5 | $0.00018 | $0.00124 |
Grade A, and why
dhpk-library-dual-testsuite-map 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 6d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Library dual-testsuite map
A library that supports multiple framework majors typically splits its source into:
src/
├── Core/ # framework-agnostic — no Illuminate / Symfony imports
└── <Framework>/ # glue layer — pulls in container, facades, etc.
And mirrors the split in tests:
tests/
├── Core/ # boots no container
└── <Framework>/ # boots Testbench / Symfony Kernel / etc.
The phpunit.xml declares both as testsuites:
<testsuites>
<testsuite name="core"><directory>tests/Core</directory></testsuite>
<testsuite name="laravel"><directory>tests/Laravel</directory></testsuite>
</testsuites>
And composer.json exposes them as scripts:
"scripts": {
"test:core": "phpunit --testsuite=core",
"test:laravel": "phpunit --testsuite=laravel",
"test:unit": ["@test:core", "@test:laravel"]
}
The skill: given an edited file path, tell the developer which testsuite to run (or both).
When to run
- After editing any
src/**file - After editing any
tests/**file - When the user asks "which tests should I run?"
When NOT to Use
- Projects with a single testsuite — this skill has nothing to do
- E2E / integration tests in a separate dir (e.g.
tests/Integration/) that runs in CI but not locally
Decision rules
Read phpunit.xml for the testsuite-to-directory mapping. Then apply:
| Edit location | Run |
|---|---|
src/Core/** only |
composer test:core |
src/Laravel/** (or other framework dir) only |
composer test:laravel |
| Both Core and framework dirs | composer test:unit (= both suites) |
tests/Core/** only |
composer test:core |
tests/Laravel/** only |
composer test:laravel |
src/Core/<X> + tests/Laravel/<X> (cross-layer) |
composer test:unit — and ask why a Core class needs a Laravel-only test (smell) |
phpunit.xml or composer.json |
composer test:unit (config touched, run everything) |
Cross-layer smell rules
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.
- 6d ago First seen · 147 lines · 181 tokens per session scan A 4c2874d02c4d
dhpk-library-dual-testsuite-map is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 181 tokens to every session and 1,244 once invoked, about $0.0009 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-09-05.
Other skills, from other repositories
test-gen
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns.
check-and-test
Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does…
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
bun-test-basics
Use for bun:test syntax, assertions, describe/it, test.skip/only/each, and basic patterns.
test-implement
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.