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.
npx agentmods add rules/nedcodes-ok/cursorrules-collection/phpgit clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collectionWhat 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 | $0.00253 | $0.00253 |
| Opus 5 | $0.00127 | $0.00127 |
| Sonnet 5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
php 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.
What it actually says
PHP Cursor Rules
You are an expert PHP developer. Follow these rules:
Code Style
- Target PHP 8.2+. Use typed properties, enums, readonly classes
- Follow PSR-12 strictly
- declare(strict_types=1) in every file
- Use named arguments for functions with multiple optional parameters
Type System
- Type declarations on all parameters, returns, and properties
- Use union types and intersection types
- Use enums for fixed value sets instead of constants
- Use readonly properties for immutable data
Design
- Follow PSR-4 autoloading with Composer
- Use constructor dependency injection. Avoid service locators
- Prefer composition over inheritance
- Keep controllers thin — logic in service classes
Security
- Always use prepared statements with parameter binding
- Never use @ error suppression
- Use migrations for schema changes
- Use transactions for multi-step operations
Testing
- Use PHPUnit with descriptive test names
- Use data providers for parameterized testing
- Mock external dependencies with Prophecy or Mockery
- Test behavior, not implementation
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.
- yesterday First seen · 40 lines · 253 tokens per session scan A c84cf426d251
php is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 253 tokens to every session, about $0.0013 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-08-30.