Borrowing it
Nothing to install: this file belongs to elmochilyas/laraskills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/elmochilyas/laraskills/main/.opencode/commands/tdd.mdgit clone --depth 1 https://github.com/elmochilyas/laraskillsWrote 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/commands/elmochilyas/laraskills/tdd)<a href="https://agentmods.dev/commands/elmochilyas/laraskills/tdd"><img src="https://agentmods.dev/badge/commands/elmochilyas/laraskills/tdd.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.1 | $0.00013 | $0.00333 |
| Opus 5 | $0.00006 | $0.00167 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
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.
What it actually says
TDD Command
Usage
Enforce a Test-Driven Development workflow using Pest 4 for Laravel 13 features.
TDD Cycle
- RED — Write a failing test first
- GREEN — Write minimal implementation to pass
- REFACTOR — Clean up while keeping tests green
Test Structure
tests/
Feature/ — 80% of tests (HTTP, database, auth)
Unit/ — 20% of tests (Actions, DTOs, Services)
Architect/ — Architecture enforcement tests
Test Types
- Feature tests: Full request/response cycle with
RefreshDatabase - Unit tests: Isolated logic for Actions, DTOs, Value Objects
- Architecture tests: Enforce conventions with Pest
->arch()
Coverage Target
php artisan test --parallel --coverage --min=80
Before Committing
- Write failing test (RED)
- Write implementation (GREEN)
- Refactor if needed (REFACTOR)
- Run
./vendor/bin/pint --test - Run
./vendor/bin/phpstan analyse --level=6 - Verify 80%+ coverage
References
- See skill:
laravel-tddfor comprehensive Pest 4 testing patterns - See rules/laravel/testing.md for testing conventions
- See rules/common/testing.md for general testing 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.
- 8d ago First seen · 52 lines · 13 tokens per session scan A d2871a0d9d5d
tdd is a command published in the GitHub repository elmochilyas/laraskills (8 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 333 once invoked, about $0.0001 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 commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.