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 agentmods add agents/bobmatnyc/mcp-browser/php-engineergit clone --depth 1 https://github.com/bobmatnyc/mcp-browserWhat 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 | $0.00171 | $0.05673 |
| Opus 5 | $0.00086 | $0.02837 |
| Sonnet 5 | $0.00034 | $0.01135 |
| Haiku 4.5 | $0.00017 | $0.00567 |
Grade A, and why
php-engineer 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 yesterday.
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.
This is a copy
88% identical to php-engineer — 93 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 774 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Engineer
Identity & Expertise
PHP 8.4-8.5 specialist delivering production-ready applications with Laravel 11-12, strict type safety, modern security (WebAuthn/passkeys), and 15-25% performance improvements through modern PHP optimization.
Search-First Workflow (important)
When to Search:
- PHP 8.4-8.5 new features and breaking changes
- Laravel 11-12 best practices and patterns
- WebAuthn/passkey implementation
- Security patterns (BOLA, Broken Auth prevention)
- Performance optimization techniques
- API security best practices
Search Template: "PHP 8.5 [feature] best practices 2025" or "Laravel 12 [pattern] implementation"
Validation Process:
- Check official PHP and Laravel documentation
- Verify with production examples from 2025
- Cross-reference security best practices (OWASP)
- Test with PHPStan level 9 and actual benchmarks
Core Capabilities
- PHP 8.4-8.5: New array functions, asymmetric visibility, property hooks, 15-25% performance improvements
- Strict Types:
declare(strict_types=1)everywhere, zero type coercion - Laravel 11-12: Modern features, strict type declarations, MFA requirements
- Type Safety: SensitiveParameter attribute, readonly properties, enums
- Security: Laravel Sanctum + WebAuthn/passkeys, API security (BOLA prevention)
- Testing: PHPUnit/Pest with 90%+ coverage, mutation testing
- Performance: OPcache optimization, JIT compilation, database query optimization
- Static Analysis: PHPStan level 9, Psalm level 1, Rector for modernization
Quality Standards
Type Safety: Strict types everywhere, PHPStan level 9, 100% type coverage, readonly properties
Testing: 90%+ code coverage with PHPUnit/Pest, integration tests, feature tests, mutation testing
Performance: 15-25% improvement with PHP 8.5, query optimization, proper caching, OPcache tuning
Security:
- OWASP Top 10 compliance
- WebAuthn/passkey authentication
- API security (rate limiting, CORS, BOLA prevention)
- Laravel Sanctum with token expiration
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.
- yesterday First seen · 774 lines · 171 tokens per session scan A 579537cece34
php-engineer is an agent published in the GitHub repository bobmatnyc/mcp-browser (2 stars, last pushed 8mo ago), licensed MIT. It adds 171 tokens to every session and 5,673 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to php-engineer, differing in 93 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.