JetBrains/phpstorm-claude-marketplace is an AI-agent plugin that connects PhpStorm with Claude Code and Codex. PHP developers use it for code review, project guidance, PHP upgrade assistance, and automatic feedback from PhpStorm inspections after edits. The catalogue contains the plugin's skills and integration components.
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/jetbrains/phpstorm-claude-marketplace/php-code-reviewnpx skills add JetBrains/phpstorm-claude-marketplace --skill php-code-reviewgit clone --depth 1 https://github.com/JetBrains/phpstorm-claude-marketplaceWrote 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/skills/jetbrains/phpstorm-claude-marketplace/php-code-review)<a href="https://agentmods.dev/skills/jetbrains/phpstorm-claude-marketplace/php-code-review"><img src="https://agentmods.dev/badge/skills/jetbrains/phpstorm-claude-marketplace/php-code-review.svg" alt="Measured on agentmods" 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.00034 | $0.00428 |
| Opus 5 | $0.00017 | $0.00214 |
| Sonnet 5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
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 6d 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.
What it actually says
PHP Code Review Skill
Use PhpStorm's inspection engine to ensure PHP code quality. This skill provides access to the same inspections shown in the IDE editor.
When to Use
- After editing PHP files (
.php,.phtml) - When user asks to review PHP code quality
- When fixing PHP-related issues
- When asked about PHP best practices for this codebase
Workflow
1. Run Inspections
Call get_inspections to analyze a PHP file:
get_inspections(
filePath: "path/to/file.php",
minSeverity: "WEAK_WARNING" # or ERROR, WARNING, INFORMATION
)
Returns problems with:
- severity: ERROR > WARNING > WEAK_WARNING > INFORMATION
- line/column: Exact location (1-based)
- description: What's wrong
- quickFixes: Available automated fixes (name + description)
2. Evaluate Results
- ERROR: Must fix - code may not work correctly
- WARNING: Should fix - potential bugs or bad practices
- WEAK_WARNING: Consider fixing - style or minor issues
- INFORMATION: Optional - suggestions for improvement
3. Apply Fixes
For issues with quick fixes, use apply_quick_fix:
apply_quick_fix(
filePath: "path/to/file.php",
line: 42,
column: 10,
quickFixName: "Safe delete '$unusedVar'"
)
Note: The quickFixName must match exactly what was returned by get_inspections. The tool re-runs highlighting at the specified location to find and apply the matching fix.
For issues without quick fixes, edit the file manually.
4. Verify
Re-run inspections to confirm issues are resolved.
What ships with it
1 file 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.
- 6d ago First seen · 63 lines · 34 tokens per session scan A b155eb4bb66d
php-code-review is a skill published in the GitHub repository JetBrains/phpstorm-claude-marketplace (33 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 428 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-30.
Other skills, from other repositories
php-best-practices
PHP 8.x modern patterns, PSR standards, and SOLID principles. Use when reviewing PHP code, checking type safety, auditing code quality, or ensuring PHP best practices. Triggers on "review PHP", "check PHP code", "audit PHP", or "PHP best practices".
check-class-length
Analyzes PHP code for class length issues. Detects classes exceeding 300 lines, God class indicators, cohesion issues, SRP violations.
check-consistency
Analyzes PHP code for consistency issues. Detects mixed coding styles, inconsistent patterns, API inconsistencies, naming convention violations.
check-comments
Analyzes PHP code for comment quality issues. Detects missing PHPDoc, outdated comments, commented-out code, opportunities for self-documenting code.
check-dependency-injection
Analyzes PHP code for dependency injection issues. Detects constructor injection usage, interface dependencies, service locator antipattern, new keyword in business logic.
check-code-style
Analyzes PHP code for style issues. Checks PSR-12 compliance, formatting consistency, whitespace usage, line length.