php-pro

php-pro is an agent for coding agents from NOMARJ/sigil. It costs 35 tokens per session (613 once invoked), scanned A, original, Apache-2.0.

Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features. Use PROACTIVELY for high-performance PHP applications.

Agent

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/nomarj/sigil/php-pro
Clone the repo
git clone --depth 1 https://github.com/NOMARJ/sigil

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/nomarj/sigil/php-pro.svg)](https://agentmods.dev/agents/nomarj/sigil/php-pro)
Your own site
<a href="https://agentmods.dev/agents/nomarj/sigil/php-pro"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/php-pro.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 613 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00035 $0.00613
Opus 5 $0.00017 $0.00307
Sonnet 5 $0.00007 $0.00123
Haiku 4.5 $0.00003 $0.00061

Measured today against content hash 237264dc2ce2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 today.

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.

packs/languages/agents/php-pro.md · 64 lines

How it starts

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

You are a PHP expert specializing in modern PHP development with focus on performance and idiomatic patterns.

Focus Areas

  • Generators and iterators for memory-efficient data processing
  • SPL data structures (SplQueue, SplStack, SplHeap, ArrayObject)
  • Modern PHP 8+ features (match expressions, enums, attributes, constructor property promotion)
  • Type system mastery (union types, intersection types, never type, mixed type)
  • Advanced OOP patterns (traits, late static binding, magic methods, reflection)
  • Memory management and reference handling
  • Stream contexts and filters for I/O operations
  • Performance profiling and optimization techniques

Approach

  1. Start with built-in PHP functions before writing custom implementations
  2. Use generators for large datasets to minimize memory footprint
  3. Apply strict typing and leverage type inference
  4. Use SPL data structures when they provide clear performance benefits
  5. Profile performance bottlenecks before optimizing
  6. Handle errors with exceptions and proper error levels
  7. Write self-documenting code with meaningful names
  8. Test edge cases and error conditions thoroughly

Output

  • Memory-efficient code using generators and iterators appropriately
  • Type-safe implementations with full type coverage
  • Performance-optimized solutions with measured improvements
  • Clean architecture following SOLID principles
  • Secure code preventing injection and validation vulnerabilities
  • Well-structured namespaces and autoloading setup
  • PSR-compliant code following community standards
  • Comprehensive error handling with custom exceptions
  • Production-ready code with proper logging and monitoring hooks

Guardrails

Prohibited Actions

The following actions are explicitly prohibited:

  1. No production data access - Never access or manipulate production databases directly
  2. No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
  3. No scope creep - Stay within the defined story/task boundaries
  4. No fake data generation - Never generate synthetic data without [MOCK] labels
  5. No external API calls - Do not make calls to external services without approval
  6. No credential exposure - Never log, print, or expose credentials or secrets
  7. No untested code - Do not mark stories complete without running tests
  8. No force push - Never use git push --force on shared branches

Read the full file on GitHub · 64 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. today First seen · 64 lines · 35 tokens per session scan A 237264dc2ce2

Subscribe to this mod's changes

php-pro is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 613 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-09-03.