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 iwritec0de/wp-dev --skill php-cleanupgit clone --depth 1 https://github.com/iwritec0de/wp-devWrote 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/iwritec0de/wp-dev/php-cleanup)<a href="https://agentmods.dev/skills/iwritec0de/wp-dev/php-cleanup"><img src="https://agentmods.dev/badge/skills/iwritec0de/wp-dev/php-cleanup/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/iwritec0de/wp-dev/php-cleanup"><img src="https://agentmods.dev/badge/skills/iwritec0de/wp-dev/php-cleanup.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.00157 | $0.03700 |
| Opus 5.5 | $0.00063 | $0.01480 |
| Sonnet 5.5 | $0.00031 | $0.00740 |
| Haiku 4.5 | $0.00016 | $0.00370 |
Grade A, and why
php-cleanup 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 1mo 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 — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP/WordPress Dead Code & Dependency Cleanup
A toolchain that replicates what Knip does for JS/TS — detect unused code, unused dependencies, missing dependencies, and dead exports — but for PHP/WordPress plugin and theme development.
Toolchain Overview
| Tool | Purpose | Detects |
|---|---|---|
composer-unused |
Unused Composer packages | Packages in require/require-dev never referenced in code |
composer-require-checker |
Missing Composer packages | Packages used in code but not declared in composer.json |
Psalm --find-unused-code |
Dead PHP code | Unused classes, methods, functions, properties, variables |
| PHP-CS-Fixer | Unused use imports |
use statements at the top of files that aren't referenced |
| PHP_CodeSniffer | Unused imports (alt) | Same as above, alternative tool |
Installation
All Tools at Once
composer require --dev \
icanhazstring/composer-unused \
maglnet/composer-require-checker \
vimeo/psalm \
php-stubs/wordpress-stubs \
friendsofphp/php-cs-fixer
Individual Installation
# Unused dependency detection
composer require --dev icanhazstring/composer-unused
# Missing dependency detection
composer require --dev maglnet/composer-require-checker
# Static analysis + dead code detection
composer require --dev vimeo/psalm
composer require --dev php-stubs/wordpress-stubs
# Unused import cleanup
composer require --dev friendsofphp/php-cs-fixer
Tool 1: composer-unused — Unused Dependencies
Detects Composer packages listed in composer.json that are never referenced anywhere in the codebase.
Usage
# Basic scan
composer unused
# JSON output for parsing
composer unused --output-format=json
# Exclude specific packages from the check
composer unused --excludePackage=php-stubs/wordpress-stubs
# Only check runtime dependencies (skip dev)
composer unused --no-dev
Configuration (composer-unused.php)
<?php
declare(strict_types=1);
use ComposerUnused\ComposerUnused\Configuration\Configuration;
use ComposerUnused\ComposerUnused\Configuration\NamedFilter;
use ComposerUnused\ComposerUnused\Configuration\PatternFilter;
return static function (Configuration $config): Configuration {
return $config
// Packages used dynamically or via WordPress hooks
->addNamedFilter(NamedFilter::fromString('php-stubs/wordpress-stubs'))
->addNamedFilter(NamedFilter::fromString('wpackagist-plugin/some-plugin'))
// Ignore all packages matching a pattern
->addPatternFilter(PatternFilter::fromString('/^ext-/'));
};
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.
- 1mo ago First seen · 443 lines · 157 tokens per session scan A 6ec00fbad869
php-cleanup is a skill published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 6mo ago), licensed MIT. It adds 157 tokens to every session and 3,700 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
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.
shiny-py-optimize
Diagnose and fix performance problems in Shiny for Python apps — slow startup, sluggish interactions, blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny for Python app is slow, hangs, recomputes too much, times out, or must support more users; when the user asks to…
phx-investigate
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional Amp subagents only when useful.
phx-trace
Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature change. Builds the call tree with mix xref callers instead of reading files one by one.
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
craft-php-guidelines
Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers…