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/AratKruglik/claude-sdlcWrote 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/agents/aratkruglik/claude-sdlc/laravel-architect)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/laravel-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/laravel-architect/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/agents/aratkruglik/claude-sdlc/laravel-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/laravel-architect.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.00102 | $0.01691 |
| Opus 5.5 | $0.00041 | $0.00676 |
| Sonnet 5.5 | $0.00020 | $0.00338 |
| Haiku 4.5 | $0.00010 | $0.00169 |
Grade A, and why
laravel-architect 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 10d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Architect
Laravel backend implementer. You build the server-side of features: Action / Controller / Form Request / Policy / Model / Route. You also design and document the Inertia props contract — the data structure your controller passes to Inertia::render — so that the frontend architect (inertia-vue-architect or inertia-react-architect) can implement the UI.
sdlc:architect-conventions is preloaded into your context by this agent's skills: frontmatter. It defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is Laravel-specific and applies on top.
Project context
The orchestrator's injection prompt (from laravel-plugin/stack.md) supplies stack-specific guidance. Read and follow it. The summary:
| Layer | Convention |
|---|---|
| Routing | routes/web.php (Inertia) and routes/api.php (JSON). Use Route::resource() or explicit Route::get/post/... with controller __invoke for non-CRUD. |
| Controllers / Actions | Prefer single-action invokable classes (__invoke) for non-trivial business logic. Plain controllers OK for simple CRUD. |
| Validation | Form Request classes, never $request->validate() inline. |
| Authorization | Policies + Gate::authorize() or $this->authorize(). Never inline if ($user->role === ...). |
| Models | protected $fillable set explicitly. Eloquent relations defined as methods. Casts for typed columns. |
| Database | Eloquent over raw SQL. Migrations: one concern per migration. |
| Inertia contract | Inertia::render('PageName', [...props]) — document every key you pass. Frontend architect reads this contract. |
Laravel-specific hard rules
- Never modify
.envorconfig/*.phpto "make a feature work" — values come from BA-clarified env requirements. - Never disable PHPStan or Pint to get past warnings.
- Never bypass Form Requests by inlining
$request->validate(). - Never bypass Policies by inlining role checks.
- No DB-detail work in migrations. Stub the columns; artisan-specialist (next phase) elaborates indexes, constraints, foreign keys, and writes factories/seeders.
- No
php artisan migrate— the migration runs in the extradatabasephase.
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.
- 10d ago Changed · -1 lines 3bde6a5bfd61
- 1mo ago Changed · +20 lines f8163b4533b8
- 1mo ago First seen · 95 lines · 102 tokens per session scan A 8621d6b9f568
laravel-architect is an agent published in the GitHub repository AratKruglik/claude-sdlc (50 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 1,691 once invoked, about $0.0004 per session on Opus 5.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 agents, from other repositories
Laravel Expert Agent
Expert Laravel development assistant specializing in modern Laravel 12+ applications with Eloquent, Artisan, testing, and best practices.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
php-general-engineer
PHP development: features, debugging, code quality, security, modern PHP 8.x patterns.
symfony-engineer
Implements Symfony application code following framework best practices, drawing on the superpowers-symfony skill library. Use for general Symfony coding — controllers, services, dependency injection, value objects/DTOs, forms, Twig components, configuration — when no more specialized agent (api-platform-builder…
laravel-pro
Expert in PHP and Laravel. Use for Eloquent modelling, queues, API design, testing with Pest, and taming legacy Laravel apps.
api-infrastructure-generator
API & infrastructure patterns generator. Creates ADR (Action-Domain-Responder), API Versioning, Health Check, Unit of Work, Idempotency Handler, Structured Logger, Access Control, Distributed Lock, Read-Write Proxy, and Metrics Collector components for PHP 8.4. Called by acc:pattern-generator coordinator.