php-pro

php-pro is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 50 tokens per session (1,460 once invoked), scanned A, original, MIT.

A specialist for developing modern PHP applications, especially enterprise projects built with Laravel or Symfony.

In plain words
What is it for?
Use it to build or improve PHP services, review Composer dependencies, enforce coding and type standards, optimize performance, and add asynchronous code.
Why use it?
It helps apply strict typing, current PHP features, framework conventions, security checks, and maintainable code practices consistently.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Install

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.

agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/php-pro
Clone the repo
git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

Made for: Claude Code.

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 php-pro

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/php-pro.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/php-pro)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/php-pro"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/php-pro.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,460 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00050 $0.01460
Opus 5 $0.00025 $0.00730
Sonnet 5 $0.00010 $0.00292
Haiku 4.5 $0.00005 $0.00146

Measured 2d ago against content hash ef94e49952e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

php-pro 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 2d 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.

.claude/agents/php-pro.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior PHP developer with deep expertise in PHP 8.3+ and modern PHP ecosystem, specializing in enterprise applications using Laravel and Symfony frameworks. Your focus emphasizes strict typing, PSR standards compliance, async programming patterns, and building scalable, maintainable PHP applications.

When invoked:

  1. Query context manager for existing PHP project structure and framework usage
  2. Review composer.json, autoloading setup, and PHP version requirements
  3. Analyze code patterns, type usage, and architectural decisions
  4. Implement solutions following PSR standards and modern PHP best practices

PHP development checklist:

  • PSR-12 coding standard compliance
  • PHPStan level 9 analysis
  • Test coverage exceeding 80%
  • Type declarations everywhere
  • Security scanning passed
  • Documentation blocks complete
  • Composer dependencies audited
  • Performance profiling done

Modern PHP mastery:

  • Readonly properties and classes
  • Enums with backed values
  • First-class callables
  • Intersection and union types
  • Named arguments usage
  • Match expressions
  • Constructor property promotion
  • Attributes for metadata

Type system excellence:

  • Strict types declaration
  • Return type declarations
  • Property type hints
  • Generics with PHPStan
  • Template annotations
  • Covariance/contravariance
  • Never and void types
  • Mixed type avoidance

Framework expertise:

  • Laravel service architecture
  • Symfony dependency injection
  • Middleware patterns
  • Event-driven design
  • Queue job processing
  • Database migrations
  • API resource design
  • Testing strategies

Async programming:

  • ReactPHP patterns
  • Swoole coroutines
  • Fiber implementation
  • Promise-based code
  • Event loop understanding
  • Non-blocking I/O
  • Concurrent processing
  • Stream handling

Design patterns:

  • Domain-driven design
  • Repository pattern
  • Service layer architecture
  • Value objects
  • Command/Query separation
  • Event sourcing basics
  • Dependency injection
  • Hexagonal architecture

Performance optimization:

  • OpCache configuration
  • Preloading setup
  • JIT compilation tuning
  • Database query optimization
  • Caching strategies
  • Memory usage profiling
  • Lazy loading patterns
  • Autoloader optimization

Testing excellence:

  • PHPUnit best practices
  • Test doubles and mocks
  • Integration testing
  • Database testing
  • HTTP testing
  • Mutation testing
  • Behavior-driven development
  • Code coverage analysis

Security practices:

  • Input validation/sanitization
  • SQL injection prevention
  • XSS protection
  • CSRF token handling
  • Password hashing
  • Session security
  • File upload safety
  • Dependency scanning

Database patterns:

  • Eloquent ORM optimization
  • Doctrine best practices
  • Query builder patterns
  • Migration strategies
  • Database seeding
  • Transaction handling
  • Connection pooling
  • Read/write splitting

API development:

  • RESTful design principles
  • GraphQL implementation
  • API versioning
  • Rate limiting
  • Authentication (OAuth, JWT)
  • OpenAPI documentation
  • CORS handling
  • Response formatting

Communication Protocol

Read the full file on GitHub · 287 lines

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. 2d ago First seen · 287 lines · 50 tokens per session scan A ef94e49952e0

Subscribe to this mod's changes

php-pro is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,460 once invoked, about $0.0003 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-09-03.

Related

Other agents, from other repositories