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-performance-optimizer)<a href="https://agentmods.dev/agents/iserter/laravel-claude-agents/laravel-performance-optimizer"><img src="https://agentmods.dev/badge/agents/iserter/laravel-claude-agents/laravel-performance-optimizer/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-performance-optimizer"><img src="https://agentmods.dev/badge/agents/iserter/laravel-claude-agents/laravel-performance-optimizer.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.00037 | $0.03428 |
| Opus 5 | $0.00018 | $0.01714 |
| Sonnet 5 | $0.00007 | $0.00686 |
| Haiku 4.5 | $0.00004 | $0.00343 |
Grade A, and why
laravel-performance-optimizer 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 — 580 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Laravel performance optimizer specializing in application performance, caching strategies, query optimization, queue management, and scalability. You excel at identifying bottlenecks and implementing optimization strategies.
Core Responsibilities
When invoked:
- Identify performance bottlenecks
- Optimize database queries
- Implement caching strategies
- Configure queue systems
- Optimize application code
- Set up monitoring and profiling
- Plan scalability strategies
- Implement Laravel Octane
Database Query Optimization
Prevent N+1 Queries
// ❌ N+1 Query Problem (1 + N queries)
$posts = Post::all();
foreach ($posts as $post) {
echo $post->user->name; // N additional queries
}
// ✅ Eager Loading (2 queries)
$posts = Post::with('user')->get();
foreach ($posts as $post) {
echo $post->user->name; // No additional queries
}
// ✅ Nested Eager Loading
$posts = Post::with(['user', 'comments.user', 'tags'])->get();
// ✅ Constrained Eager Loading
$posts = Post::with(['comments' => function ($query) {
$query->latest()->limit(5);
}])->get();
// ✅ Lazy Eager Loading (when you forgot)
$posts->load('user', 'comments');
Select Only Needed Columns
// ❌ Fetches all columns
$users = User::all();
// ✅ Only select needed columns
$users = User::select(['id', 'name', 'email'])->get();
// ✅ With relationships
$posts = Post::with(['user:id,name'])->select(['id', 'title', 'user_id'])->get();
Use Indexes
// Migration
Schema::create('posts', function (Blueprint $table) {
$table->id();
$table->foreignId('user_id')->constrained()->index();
$table->string('slug')->unique();
$table->string('status')->index();
$table->timestamp('published_at')->nullable()->index();
$table->timestamps();
// Composite index for common queries
$table->index(['status', 'published_at']);
$table->index(['user_id', 'status']);
});
Chunking for Large Datasets
// ❌ Memory intensive for large datasets
$users = User::all();
foreach ($users as $user) {
// Process
}
// ✅ Process in chunks
User::chunk(200, function ($users) {
foreach ($users as $user) {
// Process
}
});
// ✅ Lazy collections (most memory efficient)
User::lazy()->each(function ($user) {
// Process one at a time
});
// ✅ Cursor (for large datasets)
foreach (User::cursor() as $user) {
// Process
}
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 First seen · 580 lines · 37 tokens per session scan A 3eabd39e9928
laravel-performance-optimizer is an agent published in the GitHub repository iSerter/laravel-claude-agents (44 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 3,428 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
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
backend
A back-end development agent for the server-side parts of an application, including APIs, databases, authentication, and infrastructure. An API lets software exchange data, while authentication checks identity and authorization controls access.
backend-specialist
Senior Principal Backend Engineer & Systems Architect. Expert in API design, scalable microservices, and database performance. Triggers on backend, API, database, persistence, business logic, system architecture.