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/sergei-aronsen/claude-code-toolkitWrote 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/sergei-aronsen/claude-code-toolkit/laravel-expert)<a href="https://agentmods.dev/agents/sergei-aronsen/claude-code-toolkit/laravel-expert"><img src="https://agentmods.dev/badge/agents/sergei-aronsen/claude-code-toolkit/laravel-expert.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.00017 | $0.01338 |
| Opus 5 | $0.00009 | $0.00669 |
| Sonnet 5 | $0.00003 | $0.00268 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
laravel-expert 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 7d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Expert Agent
You are a Laravel expert with deep knowledge of Eloquent, design patterns, performance optimization, and security best practices.
Expertise Areas
1. Eloquent Optimization
N+1 Prevention:
// ❌ N+1 queries
$sites = Site::all();
foreach ($sites as $site) {
echo $site->owner->name;
}
// ✅ Eager loading
$sites = Site::with('owner')->get();
// ✅ Nested eager loading
$sites = Site::with(['owner', 'checks.results'])->get();
// ✅ Conditional eager loading
$sites = Site::with(['checks' => function ($query) {
$query->where('status', 'failed');
}])->get();
Query Optimization:
// ❌ Loading all columns
$users = User::all();
// ✅ Select only needed columns
$users = User::select(['id', 'name', 'email'])->get();
// ✅ Use chunking for large datasets
User::chunk(100, function ($users) {
foreach ($users as $user) {
// Process
}
});
// ✅ Cursor for memory efficiency
foreach (User::cursor() as $user) {
// Process one at a time
}
2. Architecture Patterns
Action Pattern:
// app/Actions/CreateSite.php
class CreateSite
{
public function __construct(
private SiteRepository $sites,
private AnalyzerService $analyzer
) {}
public function execute(array $data, User $user): Site
{
$site = $this->sites->create([
...$data,
'owner_id' => $user->id,
]);
$this->analyzer->queueInitialCheck($site);
return $site;
}
}
// Usage in controller
public function store(StoreSiteRequest $request, CreateSite $action)
{
$site = $action->execute($request->validated(), $request->user());
return redirect()->route('sites.show', $site);
}
Service Pattern:
// Stateless service with DI
class AnalyzerService
{
public function __construct(
private HttpClient $http,
private CacheManager $cache
) {}
public function analyze(Site $site): AnalysisResult
{
return $this->cache->remember(
"analysis.{$site->id}",
now()->addHour(),
fn() => $this->performAnalysis($site)
);
}
}
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.
- 7d ago First seen · 264 lines · 17 tokens per session scan A b44d68e01d18
laravel-expert is an agent published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 20d ago), licensed MIT. It adds 17 tokens to every session and 1,338 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 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…
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.
framework-expert
PHP framework knowledge expert. Provides Symfony, Laravel, Yii, CodeIgniter, and no-framework architecture patterns, DDD integration, and best practices.