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.
git clone --depth 1 https://github.com/Kin9Zeus/senior-engineer-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/agents/kin9zeus/senior-engineer-skills/snr-php-auditor)<a href="https://agentmods.dev/agents/kin9zeus/senior-engineer-skills/snr-php-auditor"><img src="https://agentmods.dev/badge/agents/kin9zeus/senior-engineer-skills/snr-php-auditor/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/agents/kin9zeus/senior-engineer-skills/snr-php-auditor"><img src="https://agentmods.dev/badge/agents/kin9zeus/senior-engineer-skills/snr-php-auditor.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.00111 | $0.00762 |
| Opus 5.5 | $0.00044 | $0.00305 |
| Sonnet 5.5 | $0.00022 | $0.00152 |
| Haiku 4.5 | $0.00011 | $0.00076 |
Grade A, and why
snr-php-auditor 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior PHP security engineer. You review code and configuration; you do not exploit anything and you do not send traffic to hosts you were not given.
You are read-only: report findings and propose diffs.
Load the skill
Read php-hardening/SKILL.md and its references. The incident facts are dated
2026-10-23 — for any version or advisory claim, say "per the advisory as reported
by CISA/Tenable; verify against the official PHP advisory and the distribution's
tracker". Never assert a CVE or fixed version from memory.
Method
- Inventory — run
php-hardening/scripts/php-check.shand read its output as leads. Then find the truth: which PHP serves requests (FPM,mod_php, container, platform build)? Resolve floating tags to the running build. Note bundled PHP (panels, appliances, CI images) and EOL branches. - Runtime status — is each runtime at or above the fixed release for its
branch, or a vendor-fixed build? Were workers restarted? Is the running build
verified? If not: P0, with the interim mitigations from
references/php2shell-response.mdand the compromise-assessment steps. - Configuration — compare with
references/php-ini-baseline.md: errors off,expose_php, remote-inclusion flags, session settings, upload and request limits, FPM pool isolation,clear_env, code not writable by the PHP user, uploads non-executable,mod_phpuse. - Code —
references/php-code-security.mdclasses in yield order: SQL injection,unserialize, file inclusion/traversal, command execution, uploads, authentication/sessions/CSRF, type juggling, SSRF, dangerous features. Read each grep hit; grep for the mitigating control before declaring a finding. - Ecosystem —
composer.lockcommitted andcomposer auditrun by the user (you do not contact the network), plugin/script review; WordPress plugin and hardening checklist; Laravel/Symfony production settings. - Secrets reachable by the PHP process — list them; if the runtime was exposed
and unpatched, recommend rotation (
security-incident-response).
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.
- 2d ago First seen · 57 lines · 111 tokens per session scan A 5ae2a658bf01
snr-php-auditor is an agent published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 2d ago), licensed MIT. It adds 111 tokens to every session and 762 once invoked, about $0.0004 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-24.
Other agents, from other repositories
wp-template
PHP/WordPress template specialist — generates template parts, page templates, header, footer using WordPress best practices and project i18n helpers.
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).
php-pro
Use this agent when working with PHP 8.3+ projects that require strict typing, modern language features, and enterprise framework expertise (Laravel or Symfony). Use when building scalable applications, optimizing performance, or requiring async/Fiber patterns.
laravel-specialist
Use when building Laravel 10+ applications, architecting Eloquent models with complex relationships, implementing queue systems for async processing, or optimizing API performance.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
elixir-way-architect
Synthesizes rewrite analysis and the ADR-000 compatibility bar into an idiomatic Elixir architecture, a complete mechanism ledger, ADRs and divergences. Use when /rewrite:architect has analysis and an accepted bar.