laravel-php-auto

A set of coding standards for Laravel, a PHP web framework, and PHP applications. It covers naming, folder structure, validation, security, APIs, and database access.

In plain words
What is it for?
Use it when building controllers, models, migrations, REST APIs, validation logic, and database queries with Laravel’s Eloquent ORM.
Why use it?
It keeps Laravel projects organized and helps avoid inconsistent code, unsafe input handling, and poor database or API practices.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/usrrname/cursorrules/laravel-php-auto
Clone the repo
git clone --depth 1 https://github.com/usrrname/cursorrules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,856 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01856
Opus 5 $0.00000 $0.00928
Sonnet 5 $0.00000 $0.00371
Haiku 4.5 $0.00000 $0.00186

Measured 2d ago against content hash c18ad46580ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.cursor/rules/standards/laravel-php-auto.mdc · 319 lines

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

Read the full file on GitHub · 319 lines

Changes

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.

  1. 2d ago First seen · 319 lines · 1,856 tokens per session scan A c18ad46580ce

Subscribe to this mod's changes

laravel-php-auto is a cursor rule published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo 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.