awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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/sanjeed5/awesome-cursor-rules-mdcWrote 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/sanjeed5/awesome-cursor-rules-mdc/laravel)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/laravel"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/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/sanjeed5/awesome-cursor-rules-mdc/laravel"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/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.02628 | $0.02628 |
| Opus 5 | $0.01314 | $0.01314 |
| Sonnet 5 | $0.00526 | $0.00526 |
| Haiku 4.5 | $0.00263 | $0.00263 |
Grade A, and why
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 5d 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Best Practices (2025)
This guide outlines the definitive best practices for developing robust, scalable, and maintainable Laravel applications. Adhere to these principles to ensure your codebase is clean, performant, and secure, aligning with PSR-12, PHP The Right Way, and Laravel's conventions.
1. Code Organization & Structure
1.1 Thin Controllers, Fat Models/Services
Controllers orchestrate requests; they do not contain business logic. Delegate complex operations to dedicated Service classes or Model methods.
❌ BAD: Business logic in Controller
// app/Http/Controllers/OrderController.php
class OrderController extends Controller
{
public function store(Request $request)
{
$order = new Order();
$order->user_id = Auth::id();
$order->total = $request->input('price') * 1.20; // Calculate total with tax
$order->status = 'pending';
$order->save();
// ... more logic
}
}
✅ GOOD: Delegate to a Service
// app/Services/OrderService.php
class OrderService
{
public function createOrder(array $data): Order
{
$order = new Order();
$order->user_id = $data['user_id'];
$order->total = $data['price'] * 1.20; // Business logic encapsulated
$order->status = 'pending';
$order->save();
return $order;
}
}
// app/Http/Controllers/OrderController.php
use App\Services\OrderService;
class OrderController extends Controller
{
public function __construct(private OrderService $orderService) {}
public function store(Request $request)
{
$order = $this->orderService->createOrder([
'user_id' => Auth::id(),
'price' => $request->input('price'),
]);
return response()->json($order, 201);
}
}
1.2 Centralized Validation with Form Requests
Always use Form Request classes for validation. This keeps controllers clean and validation logic reusable.
❌ BAD: Validation in Controller
// app/Http/Controllers/PostController.php
class PostController extends Controller
{
public function store(Request $request)
{
$request->validate([
'title' => ['required', 'string', 'max:255'],
'body' => ['required', 'string'],
]);
// ...
}
}
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.
- 5d ago First seen · 403 lines · 2,628 tokens per session scan A 66543e7f023a
laravel is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,570 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 2,628 tokens to every session, about $0.0131 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 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.
laravel
Core Laravel architecture and coding conventions.
skill-laravel-api
Padrões Globais para Projetos Laravel API (Context Engineering).
laravel-php-auto
Laravel and PHP Development Standards.
php-client-implementation
Guidelines for implementing MCP clients in PHP.