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 skills add JetBrains/phpstorm-claude-marketplace --skill upgrade-phpgit 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/upgrade-php)<a href="https://agentmods.dev/skills/jetbrains/phpstorm-claude-marketplace/upgrade-php"><img src="https://agentmods.dev/badge/skills/jetbrains/phpstorm-claude-marketplace/upgrade-php/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jetbrains/phpstorm-claude-marketplace/upgrade-php"><img src="https://agentmods.dev/badge/skills/jetbrains/phpstorm-claude-marketplace/upgrade-php.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01577 |
| Opus 5 | $0.00015 | $0.00788 |
| Sonnet 5 | $0.00006 | $0.00315 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
upgrade-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 10d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Upgrade Assistant
Helps upgrade a PHP project to a target PHP version by scanning for deprecations, reporting issues, applying automated fixes after confirmation, and verifying the result.
Activation and exit
- Enter when the user asks to:
- Upgrade to a specific PHP version (e.g., "upgrade to PHP 8.4")
- Fix PHP deprecations or compatibility issues
- Scan for PHP version-related problems
- Exit when all identified issues are resolved/triaged, or the user cancels.
Phase 1: Pre-check
1. Confirm target version
Ask the user for the target PHP version if not already stated.
2. Detect current PHP configuration
get_php_project_config()
This returns the configured PHP language level, interpreter details (name, path, local/remote), and runtime information (exact version, loaded extensions, debuggers). Use it to determine the current PHP version the project is targeting.
3. Check Composer project
get_composer_dependencies()
If no packages are returned, warn: "No composer.json found. Proceeding with code-only scan."
4. Confirm PHP version constraint
get_file_text_by_path(pathInProject: "composer.json")
Look for "require": { "php": "..." } and config.platform.php.
Report to the user: Current: PHP >=X.Y → Target: PHP Z.W
Phase 2: Discovery (Scan)
Scan the project to build a complete issue inventory. Do not fix anything yet.
Step 1: Find PHP files
find_files_by_glob(globPattern: "**/*.php")
Exclude vendor/ from scanning. For large projects (>200 files), scan src/, app/ first, then tests/ separately.
Step 2: Run deprecation inspections on each file
get_inspections(
filePath: "<relative-path>",
minSeverity: "WEAK_WARNING"
)
Common deprecation-related problems will have descriptions mentioning:
- Deprecated function/method usage
- PHP version-specific language level issues
- Deprecated string interpolation syntax (
${}) - Deprecated partially-supported callables
- Deprecated
implode()argument order - Deprecated serializable usage
- Deprecated cast expressions
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.
- 10d ago First seen · 215 lines · 31 tokens per session scan A 3b9abe0f82cc
upgrade-php is a skill published in the GitHub repository JetBrains/phpstorm-claude-marketplace (33 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 1,577 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
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-security
Laravel security best practices for authn/authz, validation, CSRF, mass assignment, file uploads, secrets, rate limiting, and secure deployment.
integration-fixture
Create or validate a .test integration fixture under tests/php/Integration/Fixtures.
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…
llamaindex-development
Expert guidance for LlamaIndex development including RAG applications, vector stores, document processing, query engines, and building production AI applications.
Behat BDD Testing
PHP BDD testing with Behat framework using Gherkin feature files, Mink browser extension, context classes, and Symfony integration for behavior-driven acceptance testing.