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 AsyrafHussin/agent-skills --skill laravel-testinggit clone --depth 1 https://github.com/AsyrafHussin/agent-skillsWrote 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/asyrafhussin/agent-skills/laravel-testing)<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/laravel-testing"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/laravel-testing/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/asyrafhussin/agent-skills/laravel-testing"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/laravel-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00062 | $0.01881 |
| Opus 5 | $0.00031 | $0.00941 |
| Sonnet 5 | $0.00012 | $0.00376 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
laravel-testing 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 11d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel 13 Testing — Pest PHP 4 & PHPUnit 12
Supports both Pest PHP 4 and PHPUnit 12. See Framework Detection below.
PHPUnit version note: Laravel 13 ships with
phpunit/phpunit: ^12.5.12in its defaultcomposer.json. All patterns in this skill are compatible with PHPUnit 11, 12, and 13.
Comprehensive testing guide for Laravel 13 applications. Contains 24 rules across 6 categories for writing fast, readable, and reliable tests. Supports both Pest PHP 4 and PHPUnit 12 (Laravel 13 default).
Framework Detection
Before writing or reviewing any test code, detect which testing framework the project uses:
Step 1 — Check composer.json
# Look for these in require-dev:
# "pestphp/pest" → Pest
# "phpunit/phpunit" (without pest) → PHPUnit
- If
pestphp/pestis present → use Pest syntax - If only
phpunit/phpunitis present → use PHPUnit syntax - If both are present → Pest takes priority (Pest runs on top of PHPUnit)
Step 2 — Check for tests/Pest.php
- If
tests/Pest.phpexists → Pest is configured, use Pest syntax
Step 3 — If still unclear, ask the user
"I couldn't detect the testing framework. Does this project use Pest PHP or PHPUnit?"
Syntax Reference
Test Declaration
| Pest | PHPUnit | |
|---|---|---|
| Test function | test('...', fn() => ...) |
public function test_...(): void |
| Readable name | it('...', fn() => ...) |
#[Test] public function it_...() |
| Grouping | describe('...', fn() => ...) |
Test class name / nested classes |
| Trait application | uses(RefreshDatabase::class) |
use RefreshDatabase; inside class |
| Before each | beforeEach(fn() => ...) |
protected function setUp(): void |
| After each | afterEach(fn() => ...) |
protected function tearDown(): void |
| Parameterised | ->with([...]) |
#[DataProvider] attribute |
| Global setup | uses(...)->in('Feature') in Pest.php |
Base TestCase class |
Core assertions (identical in both frameworks)
What ships with it
27 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.
- AGENTS.md 36 KB
- metadata.json 3.0 KB
- README.md 3.0 KB
- rules/auth-acting-as.md 3.3 KB
- rules/auth-sanctum.md 3.6 KB
- rules/db-assert-has.md 3.4 KB
- rules/db-assert-missing.md 3.2 KB
- rules/db-assert-soft-deletes.md 3.4 KB
- rules/factory-define.md 3.4 KB
- rules/factory-relationships.md 3.8 KB
- rules/factory-sequences.md 3.4 KB
- rules/factory-states.md 3.5 KB
- rules/fake-ai-agent.md 2.9 KB
- rules/fake-ai-data.md 3.3 KB
- rules/fake-ai-media.md 3.0 KB
- rules/fake-event.md 4.1 KB
- rules/fake-mail.md 4.7 KB
- rules/fake-notification.md 4.5 KB
- rules/fake-queue.md 4.1 KB
- rules/fake-storage.md 4.3 KB
- rules/http-assert-json-fluent.md 3.9 KB
- rules/http-assert-response.md 3.9 KB
- rules/http-refresh-database.md 4.5 KB
- rules/http-test-structure.md 4.2 KB
- rules/pest-datasets.md 5.0 KB
- rules/pest-describe-it.md 6.0 KB
- rules/pest-hooks.md 6.2 KB
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.
- 11d ago First seen · 202 lines · 62 tokens per session scan A 9be0e9cd0546
laravel-testing is a skill published in the GitHub repository AsyrafHussin/agent-skills (75 stars, last pushed 14d ago), licensed MIT. It adds 62 tokens to every session and 1,881 once invoked, about $0.0003 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
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.
refactoring-guru
Apply Refactoring.Guru-inspired rules when diagnosing code smells, choosing refactoring techniques, and stopping cleanup before uncontrolled redesign.
refactoring
Apply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-unit-test-writing
Use this skill when the user asks to write, generate, create, or add PHPUnit unit tests for a Shopware 6 source class — phrases like "write unit tests for X", "generate tests for ClassName", "create PHPUnit tests", "add test coverage", "test this class", "cover this with tests", "I need tests for", "unit test this"…