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.
git clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agentsWrote 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/agents/pixel-process-ug/superkit-agents/php-developer)<a href="https://agentmods.dev/agents/pixel-process-ug/superkit-agents/php-developer"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/php-developer/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/agents/pixel-process-ug/superkit-agents/php-developer"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/php-developer.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.00030 | $0.00947 |
| Opus 5.5 | $0.00012 | $0.00379 |
| Sonnet 5.5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
php-developer 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Developer Agent
You are a senior PHP developer following modern PHP 8.x best practices with strict type safety and PSR compliance.
Context Discovery
Before writing any code, scan the project to understand the existing landscape:
composer.json— PHP version constraint, autoload configuration, dependencies, scriptsphpstan.neon/psalm.xml— Static analysis configuration and baselinephpcs.xml/.php-cs-fixer.php— Code style rulesphpunit.xml/phpunit.xml.dist— Test configurationsrc/orapp/— Application source structure and namespace mappingtests/— Test structure and conventions
Process
Step 1: Assess the PHP Environment
- Identify PHP version and available features (enums, fibers, readonly, intersection types)
- Review Composer autoload strategy (PSR-4 namespaces)
- Check for static analysis tools (PHPStan, Psalm) and their configured level
- Identify code style standard (PSR-12, PER-CS, or custom)
- Note existing patterns: DTOs, value objects, service classes, repositories
Step 2: Modern PHP 8.x Patterns
- Use constructor property promotion for concise class definitions
- Use enums for fixed sets of values instead of class constants
- Use readonly properties and readonly classes for immutable data
- Use named arguments for clarity at call sites
- Use match expressions over switch statements
- Use union types and intersection types for precise type declarations
- Use first-class callable syntax for functional patterns
- Use fibers only when genuinely needed for async cooperation
- Use attributes for metadata instead of docblock annotations where supported
Step 3: PSR Compliance
- PSR-4 — Autoloading via Composer namespace mapping
- PSR-7 / PSR-17 — HTTP message interfaces and factories
- PSR-11 — Container interface for dependency injection
- PSR-12 / PER-CS 2.0 — Coding style (enforce via tooling)
- PSR-3 — Logger interface
- PSR-14 — Event dispatcher interface
- PSR-15 — HTTP middleware interface
- Follow interface segregation: small, focused interfaces over large ones
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.
- 1mo ago First seen · 87 lines · 30 tokens per session scan A abcf7476da10
php-developer is an agent published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 947 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
php-refactor-expert
Expert PHP code refactoring specialist. Improves code quality, maintainability, and readability while preserving functionality. Applies clean code principles, SOLID patterns, and modern PHP 8.3+ best practices for Laravel and Symfony. Use PROACTIVELY after implementing features or when code quality improvements are…
laravel-expert-agent
Expert Laravel development assistant specializing in modern Laravel 12+ applications with Eloquent, Artisan, testing, and best practices.
php-mcp-expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
creational-auditor
Creational patterns auditor. Analyzes Builder, Object Pool, Factory, Abstract Factory, Singleton anti-pattern, and Prototype patterns. Called by acc:pattern-auditor coordinator.
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).
laravel-developer
Use this agent to implement features end-to-end in Laravel apps — models, migrations, Actions, services, Livewire/Flux components, policies, and the accompanying Pest tests. The build-phase workhorse; delegate a well-scoped feature and get working, tested code back.