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 php-fpm-opcache-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/php-fpm-opcache-diagnostics)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/php-fpm-opcache-diagnostics"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/php-fpm-opcache-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/php-fpm-opcache-diagnostics"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/php-fpm-opcache-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.00049 | $0.00423 |
| Opus 5.5 | $0.00020 | $0.00169 |
| Sonnet 5.5 | $0.00010 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
php-fpm-opcache-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
Find the failure in the actual Nginx, FastCGI, PHP-FPM, and application request path.
- Establish the service, environment, time range, and affected request. Identify the serving FPM binary, pool, FastCGI endpoint, process user, and loaded configuration. Do not infer FPM settings from CLI PHP.
- Correlate Nginx, FPM, and application logs by time and request identity. Distinguish refused connections, queue delay, execution timeout, process crashes, and application exceptions.
- For worker exhaustion, inspect the process-manager mode, queue, busy workers, process limits, measured process memory, and service or container memory limit. Derive capacity from measurements while reserving capacity for the system and dependencies. Do not blindly raise pm.max_children.
- For slow requests, use available slowlogs, profiles, and metrics. Check database waits, session locks, external requests, and filesystem I/O. A larger timeout does not establish a root-cause fix.
- For stale code, inspect timestamp validation, realpath caching, preloading, and the file publication strategy. Verify OPcache in the request-serving SAPI. Resetting CLI OPcache does not prove FPM was refreshed.
- Prepare the smallest correction, validate it with the appropriate binary, and apply it within existing authorization. Use the supported graceful-update mechanism and account for active requests.
- Verify the application revision, the original request, worker health, and error rate. Keep a practical restoration path for the preceding configuration.
Do not expose a diagnostic endpoint or phpinfo to obtain configuration. Read version-matched PHP-FPM and OPcache documentation.
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 · 18 lines · 49 tokens per session scan A 1d4039d0fc88
php-fpm-opcache-diagnostics is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (8 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 423 once invoked, about $0.0002 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
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.
qauthtrailingslash
Audit API routes for the trailing-slash / 307-redirect auth bug — where a missing or extra trailing slash makes the server issue an HTTP 307 redirect and the client silently drops the Authorization header, causing intermittent 401s. Use when reviewing or debugging FastAPI/Starlette (or similar) routes, auth-token loss…
kmp-resilience
Resilience patterns for Kotlin Multiplatform — retry with exponential backoff and jitter, timeouts, circuit breakers, rate limiting, idempotency keys for safe mutation retries, and transient-vs-fatal error classification. Covers Ktor's built-in HttpRequestRetry (client) and RateLimit (server) plugins…
springboot-ticket-diagnosis
Use to diagnose a support ticket or user-visible behavior in a Spring Boot service and prove whether it is code, data, config, contract or expected behavior.
competition-graphql-rpc-drift
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for GraphQL schemas, persisted queries, RPC manifests, generated clients, OpenAPI drift, hidden operations, and contract-to-handler mismatches. Use when the user asks to inspect GraphQL or RPC requests, compare client contracts to live…
competition-custom-protocol-replay
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for custom binary or text protocol recovery, handshake reconstruction, framing, sequence control, checksums, stateful replay, and accepted-session reproduction. Use when the user asks to decode an unknown protocol, recover custom framing…