studio-backend-bundle: Skill for Claude Code

.github/skills/code-review/SKILL.md

code-review is a skill for Claude Code, Codex from pimcore/studio-backend-bundle. It costs 45 tokens per session (1,504 once invoked), scanned A, original, no licence file.

A code-review skill for evaluating Pimcore pull requests against a fixed review contract and PHP coding guidelines.

In plain words
What is it for?
It is for reviewing pull requests in Pimcore repositories.
Why use it?
It gives reviews a consistent evidence-based standard for checking PHP changes.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

This is pimcore/studio-backend-bundle's own configuration. It tells Claude Code and Codex how to work on studio-backend-bundle itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything studio-backend-bundle configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pimcore/studio-backend-bundle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pimcore/studio-backend-bundle/2026.x/.github/skills/code-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/pimcore/studio-backend-bundle

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/pimcore/studio-backend-bundle/code-review/github.svg)](https://agentmods.dev/skills/pimcore/studio-backend-bundle/code-review)
Your own site
<a href="https://agentmods.dev/skills/pimcore/studio-backend-bundle/code-review"><img src="https://agentmods.dev/badge/skills/pimcore/studio-backend-bundle/code-review/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.

agentmods 80×15 button for code-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/pimcore/studio-backend-bundle/code-review"><img src="https://agentmods.dev/badge/skills/pimcore/studio-backend-bundle/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,504 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.1 $0.00045 $0.01504
Opus 5.5 $0.00018 $0.00602
Sonnet 5.5 $0.00009 $0.00301
Haiku 4.5 $0.00005 $0.00150

Measured 1mo ago against content hash 63eab04ddf39, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

.github/skills/code-review/SKILL.md · 112 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 1mo ago First seen · 112 lines · 45 tokens per session scan A 63eab04ddf39

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository pimcore/studio-backend-bundle (20 stars, last pushed today), with no licence file. It adds 45 tokens to every session and 1,504 once invoked, about $0.0002 per session on Opus 5.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-09-01.

Related

Other skills, from other repositories

laravel-audit-architecture

Audit a Laravel application's architecture: boundaries, responsibility, coupling, duplication, and maintainability. Use when auditing architecture.

MrPunyapal/laravel-auditor · 30 tokens

laravel-audit-conventions

Audit a Laravel application for framework conventions: anti-patterns, version-appropriate APIs, and misuse of framework features. Use when auditing Laravel conventions.

MrPunyapal/laravel-auditor · 36 tokens

code-quality

PHP and Laravel code quality toolchain — static analysis with Larastan/PHPStan, code style enforcement with Pint, automated refactoring with Rector, baseline management for legacy codebases, and CI pipeline integration via GitHub Actions. Use this skill whenever the user asks to check code quality, fix linting errors…

nasrulhazim/claude · 218 tokens

php-best-practices

PHP modernization, refactoring, code review, and standards enforcement assistant for PHP 8.2+ projects. Use this skill whenever the user wants to modernize legacy PHP code, refactor messy classes or controllers, review code for smells and anti-patterns, enforce PSR-12 and strict typing standards, or integrate Rector…

nasrulhazim/claude · 220 tokens

wp-phpcs-coding-standards

Set up and run PHPCodeSniffer with the WordPress Coding Standards (WPCS) and PHPCompatibility on a plugin or theme. Covers the composer dev-dependencies and their exact (and confusingly-named) packages — squizlabs/phpcodesniffer, wp-coding-standards/wpcs, phpcompatibility/phpcompatibility-wp…

Lonsdale201/wp-agent-skills · 261 tokens

ia-php-laravel

Modern PHP 8.4 and Laravel patterns: architecture, Eloquent, migrations, queues, testing. Use when working with Laravel, Eloquent, Blade, artisan, or building/testing a framework-based PHP app. Not for php-src internals, standalone PHP libraries, or general PHP language discussion.

iliaal/whetstone · 67 tokens