laravel-tdd

laravel-tdd is a skill for Claude Code from loulanyue/awesome-claude-notes. It costs 27 tokens per session (1,804 once invoked), scanned A, a copy of laravel-tdd, MIT.

A test-driven development workflow for Laravel using PHPUnit and Pest. TDD means writing a failing test first, making it pass, and then improving the code.

In plain words
What is it for?
Use it to test PHP classes, Eloquent models, policies, jobs, notifications, endpoints, authentication, validation, and database behavior.
Why use it?
It helps catch regressions while building features, fixing bugs, or changing Laravel code that touches HTTP requests, databases, queues, or external services.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the awesome-claude-notes plugin — 106 skills, 61 commands, 28 agents shipped together

Good fit Use it to test PHP classes, Eloquent models, policies, jobs, notifications, endpoints, authentication, validation, and database behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/loulanyue/awesome-claude-notes/laravel-tdd
Install

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.

Any agent
npx skills add loulanyue/awesome-claude-notes --skill laravel-tdd
Clone the repo
git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes

Made for: Claude Code.

Or install awesome-claude-notes, the plugin that ships this one along with the rest of its 106 skills, 61 commands, 28 agents.

Wrote 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.

agentmods badge for laravel-tdd

README.md
[![agentmods](https://agentmods.dev/badge/skills/loulanyue/awesome-claude-notes/laravel-tdd/github.svg)](https://agentmods.dev/skills/loulanyue/awesome-claude-notes/laravel-tdd)
Your own site
<a href="https://agentmods.dev/skills/loulanyue/awesome-claude-notes/laravel-tdd"><img src="https://agentmods.dev/badge/skills/loulanyue/awesome-claude-notes/laravel-tdd/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.

agentmods 80×15 button for laravel-tdd

Your own site · 80×15
<a href="https://agentmods.dev/skills/loulanyue/awesome-claude-notes/laravel-tdd"><img src="https://agentmods.dev/badge/skills/loulanyue/awesome-claude-notes/laravel-tdd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,804 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.01804
Opus 5 $0.00014 $0.00902
Sonnet 5 $0.00005 $0.00361
Haiku 4.5 $0.00003 $0.00180

Measured 8d ago against content hash 31b057e4aecf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

laravel-tdd 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 8d 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.

Origin

This is a copy

91% identical to laravel-tdd — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

docs/ja-JP/skills/laravel-tdd/SKILL.md · 293 lines

How it starts

The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Laravel TDD Workflow

Test-driven development for Laravel applications using PHPUnit and Pest with 80%+ coverage (unit + feature).

When to Use

  • New features or endpoints in Laravel
  • Bug fixes or refactors
  • Testing Eloquent models, policies, jobs, and notifications
  • Prefer Pest for new tests unless the project already standardizes on PHPUnit

How It Works

Red-Green-Refactor Cycle

  1. Write a failing test
  2. Implement the minimal change to pass
  3. Refactor while keeping tests green

Test Layers

  • Unit: pure PHP classes, value objects, services
  • Feature: HTTP endpoints, auth, validation, policies
  • Integration: database + queue + external boundaries

Choose layers based on scope:

  • Use Unit tests for pure business logic and services.
  • Use Feature tests for HTTP, auth, validation, and response shape.
  • Use Integration tests when validating DB/queues/external services together.

Database Strategy

  • RefreshDatabase for most feature/integration tests (runs migrations once per test run, then wraps each test in a transaction when supported; in-memory databases may re-migrate per test)
  • DatabaseTransactions when the schema is already migrated and you only need per-test rollback
  • DatabaseMigrations when you need a full migrate/fresh for every test and can afford the cost

Use RefreshDatabase as the default for tests that touch the database: for databases with transaction support, it runs migrations once per test run (via a static flag) and wraps each test in a transaction; for :memory: SQLite or connections without transactions, it migrates before each test. Use DatabaseTransactions when the schema is already migrated and you only need per-test rollbacks.

Testing Framework Choice

  • Default to Pest for new tests when available.
  • Use PHPUnit only if the project already standardizes on it or requires PHPUnit-specific tooling.

Examples

PHPUnit Example

use App\Models\User;
use Illuminate\Foundation\Testing\RefreshDatabase;
use Tests\TestCase;

final class ProjectControllerTest extends TestCase
{
    use RefreshDatabase;

    public function test_owner_can_create_project(): void
    {
        $user = User::factory()->create();

        $response = $this->actingAs($user)->postJson('/api/projects', [
            'name' => 'New Project',
        ]);

        $response->assertCreated();
        $this->assertDatabaseHas('projects', ['name' => 'New Project']);
    }
}

Read the full file on GitHub · 293 lines

Changes

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.

  1. 8d ago First seen · 293 lines · 27 tokens per session scan A 31b057e4aecf

Subscribe to this mod's changes

laravel-tdd is a skill published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 1,804 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to laravel-tdd, differing in 9 lines, and is treated as a copy.

Related

Other skills, from other repositories

ring:running-dev-cycle

Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or…

LerianStudio/ring · 122 tokens

ring:instrumenting-streaming-events

Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…

LerianStudio/ring · 102 tokens

armada-tdd

Test-driven development for armada workers. Use before writing any implementation. Triggers on: TDD, failing test, test first, write a test.

rafmacalaba/armada · 36 tokens

test-first

Use when implementing any feature, bugfix, or refactor that has a testable outcome. Activate for keywords like "TDD", "test-first", "red-green", "write the test first", "implement ", "fix ". Enforces the red-green-refactor discipline -- write a failing test, make it pass with the smallest change, refactor with tests…

duthaho/claudekit · 106 tokens

django-tdd

Django testing strategies with pytest-django, TDD methodology, factoryboy, mocking, coverage, and testing Django REST Framework APIs.

hashgraph-online/awesome-codex-plugins · 32 tokens

tdd-cycle

Enforce the Red-Green-Refactor TDD cycle.

Acendas/shipyard · 17 tokens