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 skills add dayfinggg/openai-codex-agent-skills --skill symfony-diagnosticsgit clone --depth 1 https://github.com/dayfinggg/openai-codex-agent-skillsWrote 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/dayfinggg/openai-codex-agent-skills/symfony-diagnostics)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/symfony-diagnostics"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/symfony-diagnostics/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/skills/dayfinggg/openai-codex-agent-skills/symfony-diagnostics"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/symfony-diagnostics.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.00032 | $0.00347 |
| Opus 5.5 | $0.00013 | $0.00139 |
| Sonnet 5.5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
symfony-diagnostics 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.
What it actually says
Establish the Symfony application, relevant request or time interval, and available project tools. Select the sharpest evidence source already identified by the task.
Read host integration once for the imported procedures.
| Symptom or available evidence | Read |
|---|---|
| The cause is unexplained and the evidence source is unknown | Request triage |
| A failed or slow request has a usable profiler token | Profiler debugging |
| The question spans requests, time, frequency, or log context | Log investigation |
| An injected service, tag, listener, or decorator is wrong | Service inspection |
| An environment variable is missing, stale, or loaded unexpectedly | Environment diagnostics |
Skip triage when the task already identifies the correct source. Keep tool-runtime failures separate from application failures. For a suspected Mate PHP runtime problem, use the PHP environment procedure. For dependency identity or an API-version mismatch, use PHP dependency versions.
Use installed Mate capabilities when available. Otherwise inspect the same evidence through the application's existing supported CLI, profiler, and logs. Do not install Mate or change production diagnostics merely to satisfy a procedure's example. Never expose raw secret values.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 22 lines · 32 tokens per session scan A 16fcefba4080
symfony-diagnostics is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (8 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 347 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-10-30.
Other skills, from other repositories
sentry-php-sdk
Full Sentry SDK setup for PHP. Use when asked to "add Sentry to PHP", "install sentry/sentry", "setup Sentry in PHP", or configure error monitoring, tracing, profiling, logging, metrics, crons, or AI monitoring for PHP applications. Supports plain PHP, Laravel, and Symfony.
kirby-ide-support
Improves IDE autocomplete and static analysis in Kirby projects with PHPDoc hints and Kirby IDE helper generation. Use when types are missing or IDE support is degraded.
wp-phpstan-static-analysis
Run PHPStan static analysis on a WordPress plugin or theme using szepeviktor/phpstan-wordpress. Covers the composer dev-dependencies and what is pulled transitively (phpstan/phpstan ^2.0, php-stubs/wordpress-stubs), the optional phpstan/extension-installer that auto-registers the extension, the phpstan.neon.dist…
php-quality-tooling
Use when setting up PHPStan, Rector, or PHP-CS-Fixer on a non-Laravel PHP project, incl. CI wiring. Do NOT use for Laravel (Pint/Larastan), tests, or syntax.
wp-phpstan
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
phpstan-phpcs-conflict-resolution
Resolves genuine conflicts between Drupal coder (PHPCS) and PHPStan level 8, and encodes the non-obvious mechanics of PHPStan suppressions in Drupal codebases. Use when the two tools give contradictory instructions on the same line, when a @phpstan-ignore "does not work", or on hook-docblock / missingType conflicts.…