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.
git clone --depth 1 https://github.com/morodomi/tdd-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/plugins/morodomi/tdd-skills/tdd-laravel)<a href="https://agentmods.dev/plugins/morodomi/tdd-skills/tdd-laravel"><img src="https://agentmods.dev/badge/plugins/morodomi/tdd-skills/tdd-laravel/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/plugins/morodomi/tdd-skills/tdd-laravel"><img src="https://agentmods.dev/badge/plugins/morodomi/tdd-skills/tdd-laravel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tdd-laravel 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.
What it actually says
{
"name": "tdd-laravel",
"description": "Laravel-specific quality tools for TDD workflow. Pest Laravel Plugin, HTTP tests, Eloquent patterns.",
"author": {
"name": "morodomi"
},
"repository": "https://github.com/morodomi/tdd-skills",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 34 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 10 lines scan A e301a344f6df
tdd-laravel is a plugin published in the GitHub repository morodomi/tdd-skills (8 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
superpowers-laravel
Laravel-focused skills for Claude Code: TDD (Pest/PHPUnit), migrations, queues, quality checks (Pint/Insights), and pragmatic architecture patterns — Sail and non-Sail compatible.
python-development
Python development toolkit - TDD with pytest, code refactoring with complexity metrics, performance profiling, async patterns, uv package management, dead code detection, comment auditing, project scaffolding, deep Pydantic v2.13 guide (validators/serializers/strict/performance/security/PydanticAI+Logfire) with v1…
msbaek-tdd
Java + Spring Boot TDD workflow plugin with requirements input drafting, RGB cycle, feature-level autonomous implementation, Cucumber acceptance testing, local tidying, system-wide refactoring, and 18 optional refactoring skills. Plan phase and Web App acceptance/skeleton setup now delegate to dedicated agents instead.
pest
Pest testing suite skills. Philosophy, organization, factories, datasets, arch testing, mocking decisions.
python
Python code quality: ruff linting (ZERO noqa), type checking (ZERO type:ignore), clean code (SOLID), TDD with pytest.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.