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 skills/jeeinn/claude-skills/php-code-reviewnpx skills add jeeinn/claude-skills --skill php-code-reviewgit clone --depth 1 https://github.com/jeeinn/claude-skillsWhat 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.00030 | $0.02655 |
| Opus 5 | $0.00015 | $0.01327 |
| Sonnet 5 | $0.00006 | $0.00531 |
| Haiku 4.5 | $0.00003 | $0.00265 |
Grade A, and why
php-code-review 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 3d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Code Review Expert
This skill provides comprehensive PHP code review capabilities, combining automated analysis with expert-level insights for PHP7 and PHP8 development.
Quick Start
- Automated Security Scan: Use
scripts/php-security-scanner.phpfor initial vulnerability detection - Code Style Check: Apply configurations from
references/php-cs-fixer-config.md - Manual Review: Follow the systematic review process outlined below
- Report Generation: Use the structured output format for consistent documentation
Available Resources
- Scripts:
php-security-scanner.php- Automated security vulnerability scanner - References:
php-cs-fixer-config.md- Ready-to-use PHP CS Fixer configurations - Examples:
before-after-refactor.md- Real-world refactoring examples - Templates:
review-report-template.md- Comprehensive review report formatquick-checklist.md- 30-minute quick review checklist
Core Review Areas
1. Naming Conventions Check
Class Naming
- PSR-4 Compliance: Class names must match file names
- CamelCase: Use PascalCase for class names (e.g.,
UserController) - Suffix Patterns:
- Controllers end with
Controller(e.g.,UserController) - Models end with
Modelor use singular nouns (e.g.,User) - Services end with
Service(e.g.,EmailService)
- Controllers end with
Method Naming
- camelCase: Methods use camelCase (e.g.,
getUserName()) - Verb-Noun Pattern: Start with action word (e.g.,
validateInput(),processOrder()) - Boolean Methods: Use is/has/can prefix (e.g.,
isValid(),hasPermission())
Variable Naming
- camelCase: Variables use camelCase (e.g.,
$userName) - Descriptive: Use meaningful names (e.g.,
$customerEmailnot$e) - Constants: UPPER_SNAKE_CASE (e.g.,
MAX_RETRY_COUNT)
Database Naming
- Table Names: snake_case, plural (e.g.,
user_profiles) - Column Names: snake_case (e.g.,
created_at) - Foreign Keys:
{singular_table}_id(e.g.,user_id)
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 293 lines · 30 tokens per session scan A 71b44d34c1da
php-code-review is a skill published in the GitHub repository jeeinn/claude-skills (5 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 2,655 once invoked, about $0.0002 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-31.
Other skills, from other repositories
laravel-actions
Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions. Use when implementing reusable action classes (object/controller/job/listener/command), converting service classes/controllers/jobs into actions, orchestrating workflows via faked actions, or debugging action entrypoints and wiring.
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization…
routes
Generate route configuration for CatchAdmin module.
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.
create-module
Scaffold a new Marko module — a self-contained Composer package with composer.json, namespaced src/, and Pest tests. Use this skill whenever the user asks to create, add, or scaffold a new Marko module or package. Concrete triggers: 'create a module named payment', 'scaffold an acme/blog package', 'add a new module…