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/usrrname/cursorrulesWrote 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/usrrname/cursorrules/laravel-php-auto)<a href="https://agentmods.dev/rules/usrrname/cursorrules/laravel-php-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/laravel-php-auto/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/usrrname/cursorrules/laravel-php-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/laravel-php-auto.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.01856 |
| Opus 5.5 | $0.00000 | $0.00742 |
| Sonnet 5.5 | $0.00000 | $0.00371 |
| Haiku 4.5 | $0.00000 | $0.00186 |
Grade A, and why
laravel-php-auto 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 1mo 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel and PHP Development Standards
This rule enforces best practices, coding standards, and architectural patterns for Laravel and PHP development.
Critical Rules
- Follow Laravel naming conventions for controllers, models, and other components
- Use Laravel's built-in features rather than reinventing functionality
- Structure code according to Laravel's MVC architecture
- Adhere to Laravel's folder structure
- Implement proper validation and error handling
- Follow RESTful design principles for API development
- Use Laravel's Eloquent ORM for database interactions
- Implement proper security measures against common web vulnerabilities
Laravel Naming Conventions
Controllers
- Use singular PascalCase + "Controller" suffix (e.g.,
UserController) - RESTful action names: index, create, store, show, edit, update, destroy
Models
- Use singular PascalCase (e.g.,
User,Product) - Model properties and relationships should use camelCase
Migrations
- Use descriptive names with timestamps (e.g.,
2023_01_01_000000_create_users_table) - Table names should be plural snake_case
Routes
- Use plural kebab-case for resource routes (e.g.,
/api/user-profiles) - Group related routes using namespaces and middlewares
PHP Code Style
- Follow PSR-12 coding standard for PHP code structure
- Use strict typing
- Use type declarations for method parameters and return types
- Prefer explicit visibility declarations (public, protected, private)
- Use null coalescing operators and other modern PHP features
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.
- 1mo ago First seen · 319 lines · 1,856 tokens per session scan A c18ad46580ce
laravel-php-auto is a cursor rule published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 1,856 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
Laravel: Eloquent, Form Requests, policies.
laravel-php-83-cursorrules-prompt-file
Cursor rules for Laravel development with PHP 8.3 integration.
laravel-package-development-guidelines
A set of coding rules for building Laravel packages, which are reusable extensions for Laravel applications. It covers package structure, code style, helper functions, type safety, editor suggestions, and documentation.
laravel-package-coding-standards
A set of coding rules for Laravel packages, with conventions for names and code across several development areas.
laravel-package-structure
A set of coding rules for organising a Laravel package, a reusable extension for Laravel applications.
django
Django: models, views, ORM best practices.