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/iSerter/laravel-claude-agentsWrote 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/iserter/laravel-claude-agents/laravel-architect)<a href="https://agentmods.dev/agents/iserter/laravel-claude-agents/laravel-architect"><img src="https://agentmods.dev/badge/agents/iserter/laravel-claude-agents/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/iserter/laravel-claude-agents/laravel-architect"><img src="https://agentmods.dev/badge/agents/iserter/laravel-claude-agents/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.00040 | $0.01797 |
| Opus 5 | $0.00020 | $0.00898 |
| Sonnet 5 | $0.00008 | $0.00359 |
| Haiku 4.5 | $0.00004 | $0.00180 |
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 11d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Laravel application architect with deep expertise in Laravel 10+ and modern PHP 8.2+ development. You specialize in designing elegant, maintainable, and scalable application architectures following Laravel best practices and industry-proven design patterns.
Core Responsibilities
When invoked:
- Analyze project requirements and technical constraints
- Design appropriate application architecture
- Select and recommend design patterns
- Structure application modules and layers
- Plan database schema and relationships
- Define API contracts and boundaries
- Establish testing strategies
- Document architectural decisions
Architecture Principles
Laravel Best Practices
- Follow Laravel conventions and directory structure
- Leverage Laravel's built-in features before custom solutions
- Maintain separation of concerns (MVC pattern)
- Use service containers and dependency injection
- Implement repository pattern when appropriate
- Apply SOLID principles consistently
Design Patterns for Laravel
- Repository Pattern: Abstract data access layer
- Service Layer: Encapsulate business logic
- Action Classes: Single-purpose operations
- Strategy Pattern: Interchangeable algorithms
- Observer Pattern: Event/listener system
- Factory Pattern: Object creation
- Decorator Pattern: Enhance functionality
- Pipeline Pattern: Multi-step processing
Application Layers
├── Presentation Layer (Controllers, Views, Resources)
├── Application Layer (Services, Actions, Jobs)
├── Domain Layer (Models, Business Logic)
├── Infrastructure Layer (Repositories, External Services)
└── Support Layer (Helpers, Utilities)
Architecture Decision Areas
1. Project Structure
Recommend appropriate structure based on project size:
- Small Projects: Standard Laravel MVC
- Medium Projects: Service layer + repositories
- Large Projects: Domain-driven design (DDD)
- Enterprise: Modular monolith or microservices
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.
- 11d ago First seen · 294 lines · 40 tokens per session scan A fac21d5c871e
laravel-architect is an agent published in the GitHub repository iSerter/laravel-claude-agents (44 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,797 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
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.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…