php-8.1

A set of PHP 8.1 coding rules covering features added in that version, including enumerations, readonly properties, and intersection types.

In plain words
What is it for?
Use it when writing or reviewing PHP 8.1 code. It gives guidance on enums, storing enum values, enum behavior, readonly data, and newer type declarations.
Why use it?
It helps developers represent fixed choices and stricter type requirements clearly, while using PHP 8.1 features consistently.

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/mitas/cursor-rules/php-8.1
Clone the repo
git clone --depth 1 https://github.com/mitas/cursor-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,210 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.02210
Opus 5 $0.00000 $0.01105
Sonnet 5 $0.00000 $0.00442
Haiku 4.5 $0.00000 $0.00221

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

Security

Grade A, and why

php-8.1 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 yesterday.

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/php-8.1.mdc · 342 lines

How it starts

The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PHP 8.1 Features and Best Practices

Overview

PHP 8.1 builds upon the foundation of PHP 8.0 with new features, performance improvements, and enhanced type safety. This document outlines the key features introduced in PHP 8.1 and provides best practices for their implementation.

Key Language Features

Enumerations (Enums)

PHP 8.1 introduces first-class enumerations, allowing for strongly typed sets of possible values.

enum Status {
    case Draft;
    case Published;
    case Archived;
}

// Usage
function updateStatus(Post $post, Status $status) {
    $post->status = $status;
    
    match($status) {
        Status::Draft => $this->sendDraftNotification(),
        Status::Published => $this->publish(),
        Status::Archived => $this->archive()
    };
}

$post->updateStatus(Status::Published);

Best Practices:

  • Use enums instead of constants for representing a fixed set of possible values
  • Use backed enums (enum Status: string {...}) when you need to store the value in a database
  • Implement methods within enums to encapsulate behavior related to each enum value
  • Use enums as type declarations for method parameters and return types
  • Consider implementing interfaces in enums when they need to fit into a type system

Readonly Properties

The readonly modifier prevents properties from being modified after initialization.

class User {
    public function __construct(
        public readonly string $id,
        public readonly string $name,
        public readonly string $email
    ) {}
}

$user = new User('1', 'John', '[email protected]');
// $user->name = 'Jane'; // This would trigger an error

Best Practices:

  • Use readonly for properties that should not change after object creation
  • Combine with constructor property promotion for concise immutable value objects
  • Use for data transfer objects (DTOs) and entities
  • Consider using readonly properties instead of getter methods in simple cases
  • Remember that readonly applies to the property, not the objects it might reference

Read the full file on GitHub · 342 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. yesterday First seen · 342 lines · 2,210 tokens per session scan A e816cccc4d76

Subscribe to this mod's changes

php-8.1 is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,210 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.