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/ConlinJoe/ai-platformWrote 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/rules/conlinjoe/ai-platform/30-laravel)<a href="https://agentmods.dev/rules/conlinjoe/ai-platform/30-laravel"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/30-laravel/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/rules/conlinjoe/ai-platform/30-laravel"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/30-laravel.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.00000 | $0.01346 |
| Opus 5.5 | $0.00000 | $0.00538 |
| Sonnet 5.5 | $0.00000 | $0.00269 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
30-laravel 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 4d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This rule applies to Laravel web applications (laravel-webapp). Do not
apply it to Roots/Radicle/Sage WordPress projects (roots-radicle) or
other non-Laravel stacks.
Backend
For tasks involving:
- Laravel
- Livewire
- Business logic
- Database design
- APIs
- Performance
- Architecture
- Refactoring
- Testing
Automatically consult Laravel Boost when available. Laravel web
applications are expected to have Boost; if it is missing, diagnose it
and continue with Current-First official docs. Do not add Boost to
user-global MCP. Install Boost only with Laravel's native installer
(composer require laravel/boost --dev then php artisan boost:install)
after approval.
Laravel Rules
Architecture
- Follow Laravel conventions appropriate to the project's installed
Laravel ecosystem (or the verified current stable ecosystem for
greenfield). Do not use historically familiar conventions from model
memory — see Current-First Engineering in
00-platform. - Follow Framework-Native First in
00-platform: use the installed Laravel ecosystem's native capabilities before parallel infrastructure or extra packages. - Keep controllers responsible only for HTTP request and response handling.
- Blade views render prepared data. Queries, persistence, content
parsing, and service orchestration belong in controllers, actions,
composers, or services. Presentation conditions, loops, formatting,
and class selection may stay in Blade. See
21-stack-architecture. - Place business logic in services or domain classes.
- Keep models focused on persistence, relationships, casts, and scopes.
- Prefer dependency injection over facades when practical.
Database
- Use Eloquent unless there is a demonstrated performance reason not to.
- Use foreign key constraints.
- Follow Laravel naming conventions.
- Create focused migrations.
Frontend
Preferred stack (unversioned; subordinate to Current-First Engineering
in 00-platform):
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.
- 4d ago Changed · +6 lines 2d7010f5a445
- 20d ago Changed · +7 lines b521ea2a71a5
- 2mo ago First seen · 175 lines · 0 tokens per session scan A b499931b500c
30-laravel is a cursor rule published in the GitHub repository ConlinJoe/ai-platform (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,346 tokens. 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 cursor rules, from other repositories
laravel-php-83-cursorrules-prompt-file
Cursor rules for Laravel development with PHP 8.3 integration.
laravel-package-coding-standards
A set of coding rules for Laravel packages, with conventions for names and code across several development areas.
guzzle
Definitive guidelines for using Guzzle HTTP client in PHP, focusing on robust client configuration, effective middleware, PSR-18 interoperability, and testability.
laravel
Definitive guide for writing clean, performant, and secure Laravel applications, emphasizing modern best practices and common pitfalls.
backend
Essential backend patterns and commands for PHP/Symfony.
laravel
Core Laravel architecture and coding conventions.