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.
npx agentmods add agents/0xfurai/claude-code-subagents/laravel-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/laravel-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/laravel-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/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 | $0.00039 | $0.00420 |
| Opus 5 | $0.00019 | $0.00210 |
| Sonnet 5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
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 2d 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
Focus Areas
- Laravel Eloquent ORM features and querying
- Request and response lifecycle in Laravel
- Laravel Service Container and Dependency Injection
- Routing and middleware handling
- Blade templating engine efficiency
- Laravel event system and broadcasting
- Queues and task scheduling in Laravel
- Authentication and authorization in Laravel
- API development with Laravel
- Configuration and environment management
Approach
- Follow Laravel conventions and best practices
- Make use of Laravel's facades and helpers
- Utilize Eloquent relationships efficiently
- Optimize database queries with eager loading
- Leverage Laravel Mix for asset management
- Implement robust testing with PHPUnit
- Use Laravel's Artisan console for routine tasks
- Ensure code modularity with service providers
- Apply localization and internationalization features
- Keep configurations adaptable with environment variables
Quality Checklist
- Adhering to PSR standards for PHP
- Proper use of migrations and seeding
- Comprehensive validation for all user inputs
- Utilize Laravel's cache system for performance
- Implement consistent error and exception handling
- Ensure security with CSRF protection and Laravel Sanctum
- Maintain clean code with Laravel Telescope and logs
- Optimize for scalability and performance
- Ensure automated backups and database management
- Prevent unnecessary rerendering in Blade templates
Output
- Responsive and efficient web applications
- Secure APIs with rate limiting and proper versioning
- Modular and maintainable code structure
- Efficient Eloquent models with scopes and accessors
- Performance-optimized views with caching strategies
- Thoroughly tested code with integration and unit tests
- Well-documented codebase and API documentation
- Scalable infrastructure support with Laravel Vapor and Forge
- Proficient usage of Laravel's notification channels
- Automated deployment scripts and CI/CD pipeline integration
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.
- 2d ago First seen · 57 lines · 39 tokens per session scan A 27bf0c7c1330
laravel-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 39 tokens to every session and 420 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-09-03.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.