Borrowing it
Nothing to install: this file belongs to symfony/ai-demo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/symfony/ai-demo/main/.agents/skills/mate-php-environment-check/SKILL.mdgit clone --depth 1 https://github.com/symfony/ai-demoWrote 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/skills/symfony/ai-demo/mate-php-environment-check)<a href="https://agentmods.dev/skills/symfony/ai-demo/mate-php-environment-check"><img src="https://agentmods.dev/badge/skills/symfony/ai-demo/mate-php-environment-check.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.00536 |
| Opus 5 | $0.00042 | $0.00268 |
| Sonnet 5 | $0.00017 | $0.00107 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
mate-php-environment-check 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- php-environment-check — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP environment check
server-info takes no arguments and returns php_version, operating_system, operating_system_family, and extensions (the extensions loaded for this runtime). Calling it is trivial; the judgment is knowing when a failure is the runtime, not the code, and reading the result against what a feature needs.
server-info accepts --format: json to parse the result, toon (when helgesverre/toon is installed) for the smallest context footprint. The loaded-extension list is long, so pass --format=json when you only need to test for one extension.
When to reach for it
Reach for server-info when a Mate tool fails or behaves oddly while the application under inspection looks fine. That gap usually means the runtime running Mate, not the app.
- Container inspection returns nothing or errors.
symfony-services/symfony-service-detailparse the dumped container XML with SimpleXML. Ifsimplexmlis absent fromextensions, that parse fails and the service map comes back empty regardless of the app. Check forsimplexmlbefore assuming the container was never compiled. - Mate itself refuses to run or a feature is missing. Mate requires PHP >= 8.2. Read
php_versionbefore blaming config; an old CLI PHP on the box is a common cause. - Path or behavior differs from expectation.
operating_system_family(WindowsvsLinux/Darwin) explains divergent path handling or line endings.
Reading
extensionsis the loaded list for this SAPI, not the installed-but-disabled list. Absent means not loaded for the runtime Mate is using, which is enough on its own to explain a dependent tool failing.- The PHP running the Mate CLI may differ from the one serving the app (different SAPI, different version).
server-inforeports the CLI runtime, so a mismatch here versus what the app runs is itself a finding.
Do not use this to diagnose application behavior. It answers one question: is the environment the reason a tool did not work.
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.
- 8d ago First seen · 26 lines · 84 tokens per session scan A b218e6d5f93b
mate-php-environment-check is a skill published in the GitHub repository symfony/ai-demo (47 stars, last pushed 9d ago), licensed MIT. It adds 84 tokens to every session and 536 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
system-information
Resolve which dependency versions are actually installed, from composer show and composer.lock, when diagnosing version-specific behavior such as a method, argument or class that does not exist in the release that is really running. For the PHP runtime itself (version, OS, loaded extensions) use the…
php-environment-check
Check the PHP runtime with server-info, its version, OS, and loaded extensions. Reach for it when a Mate tool itself fails or a capability is missing and you suspect the environment, a missing extension or an old PHP, rather than the app or its config. Not for diagnosing app behavior (profiler, log investigation) or…
Behat BDD Testing
PHP BDD testing with Behat framework using Gherkin feature files, Mink browser extension, context classes, and Symfony integration for behavior-driven acceptance testing.
php-expert
Expert-level PHP development with PHP 8+, Laravel, Composer, and modern best practices. Use when the user mentions Laravel, Composer, Symfony, PHPUnit, or PSR standards, or when the task involves PHP 8+ Features, Object-Oriented PHP, Modern PHP, or Constructor Property Promotion.
scraperapi-php-sdk
Best-practices reference for the ScraperAPI PHP SDK (scraperapi/sdk Composer package). Consult whenever the user is writing, debugging, or reviewing PHP code that calls ScraperAPI. Use when user asks: "scrape a website with PHP and ScraperAPI", "ScraperAPI PHP example", "how do I use the ScraperAPI PHP SDK", "PHP…
pn-php-scaffolding
Scaffolds new PHP API projects (Laravel, Slim) or routes. Use when adding a new controller/service; covers PSR standards, Composer hygiene, Laravel conventions, and idiomatic PHP 8.x patterns.