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 anilcancakir/my-claude-code --skill laravel-testinggit clone --depth 1 https://github.com/anilcancakir/my-claude-codeWrote 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/anilcancakir/my-claude-code/laravel-testing)<a href="https://agentmods.dev/skills/anilcancakir/my-claude-code/laravel-testing"><img src="https://agentmods.dev/badge/skills/anilcancakir/my-claude-code/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/anilcancakir/my-claude-code/laravel-testing"><img src="https://agentmods.dev/badge/skills/anilcancakir/my-claude-code/laravel-testing.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.00113 | $0.01363 |
| Opus 5 | $0.00056 | $0.00681 |
| Sonnet 5 | $0.00023 | $0.00273 |
| Haiku 4.5 | $0.00011 | $0.00136 |
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 9d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Testing
PHPUnit + Dusk testing patterns for Laravel 12+.
Feature Tests
<?php
namespace Tests\Feature;
use App\Models\Order;
use App\Models\User;
use Illuminate\Foundation\Testing\RefreshDatabase;
use Tests\TestCase;
class OrderTest extends TestCase
{
use RefreshDatabase;
/**
* Test order creation endpoint.
*/
public function test_user_can_create_order(): void
{
$user = User::factory()->create();
$response = $this
->actingAs($user)
->postJson('/api/orders', [
'total' => 100.00,
'items' => [
['product_id' => 1, 'quantity' => 2],
],
]);
$response
->assertCreated()
->assertJsonStructure([
'id',
'status',
'total',
]);
$this->assertDatabaseHas('orders', [
'user_id' => $user->id,
'status' => 'pending',
]);
}
/**
* Test authentication requirement.
*/
public function test_order_creation_requires_authentication(): void
{
$this->postJson('/api/orders', [])
->assertUnauthorized();
}
/**
* Test validation rules.
*/
public function test_order_validates_required_fields(): void
{
$user = User::factory()->create();
$this
->actingAs($user)
->postJson('/api/orders', [])
->assertUnprocessable()
->assertJsonValidationErrors(['total', 'items']);
}
}
Unit Tests
<?php
namespace Tests\Unit;
use App\Services\TaxCalculator;
use PHPUnit\Framework\TestCase;
class TaxCalculatorTest extends TestCase
{
/**
* Test tax calculation with 20% rate.
*/
public function test_calculates_tax_correctly(): void
{
$calculator = new TaxCalculator(taxRate: 0.20);
$result = $calculator->calculate(100.00);
$this->assertEquals(120.00, $result);
}
/**
* Test zero amount returns zero.
*/
public function test_zero_amount_returns_zero(): void
{
$calculator = new TaxCalculator(taxRate: 0.20);
$this->assertEquals(0.00, $calculator->calculate(0.00));
}
}
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.
- 9d ago First seen · 255 lines · 113 tokens per session scan A 86485675ba56
laravel-testing is a skill published in the GitHub repository anilcancakir/my-claude-code (5 stars, last pushed 7mo ago), licensed MIT. It adds 113 tokens to every session and 1,363 once invoked, about $0.0006 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-31.
Other skills, from other repositories
java-unit-test
A code-generation guide for Java unit tests in Spring Boot projects. Unit tests check one small piece of code in isolation; Spring Boot is a Java framework for building web applications and services.
typescript
TypeScript strict mode with eslint and jest.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
cpp-testing
A guide for testing C++17/20 code with GoogleTest, GoogleMock, CMake, and CTest. It covers unit and integration tests, test discovery, coverage, and sanitizers.