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 agentmods add commands/iwritec0de/wp-dev/wp-testgit clone --depth 1 https://github.com/iwritec0de/wp-devWhat 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 | $0.00016 | $0.00491 |
| Opus 5 | $0.00008 | $0.00246 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
wp-test 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 yesterday.
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
/wp-test
Run the test suite for the current WordPress project. Auto-detects the test framework and runner.
Skills
Load the wp-testing skill for PHPUnit patterns, WordPress test factories, and testing methodology.
Usage
Parse the user's arguments:
phporphpunit— Run PHPUnit testsjsorjest— Run JavaScript tests (Jest or wp-scripts)all— Run both PHP and JS tests- No arguments — Auto-detect and run whatever is configured
Detection Logic
PHPUnit
- Check for
vendor/bin/phpunit - Check for
phpunit.xmlorphpunit.xml.dist - If both exist, run:
vendor/bin/phpunit - If only the binary exists, warn about missing config
- If neither exists, suggest:
composer require --dev phpunit/phpunit
Jest / wp-scripts
- Check for
node_modules/.bin/jestornode_modules/.bin/wp-scripts - Check
package.jsonfortestscript - Prefer
npx wp-scripts test-unit-jsfor Gutenberg block projects (if@wordpress/scriptsis a dependency) - Fall back to
npx jestif jest is available - If neither exists, suggest:
npm install --save-dev @wordpress/scripts
Execution
Run the detected test command via Bash. Show the full output to the user.
Common Options
--coverage— Add code coverage flag (--coveragefor PHPUnit,--coveragefor Jest)--filter <pattern>— Filter tests by name (PHPUnit--filter, Jest pattern arg)
Output
After tests complete, summarize:
- Total tests run
- Passed / Failed / Skipped counts
- If failures exist, show the failing test names and file locations
Rules
- Never modify test files — this command is read-only + execute
- If tests fail, suggest fixes but don't auto-apply
- Always use project-local binaries (
vendor/bin/,node_modules/.bin/) over global
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.
- yesterday First seen · 57 lines · 16 tokens per session scan A 157e1cd151ae
wp-test is a command published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 491 once invoked, about $0.0001 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.