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 dr-robert-li/cowork-wordpress-expert --skill testinggit clone --depth 1 https://github.com/dr-robert-li/cowork-wordpress-expertWrote 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/dr-robert-li/cowork-wordpress-expert/testing)<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/testing"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/testing/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/dr-robert-li/cowork-wordpress-expert/testing"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/testing.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.00043 | $0.02787 |
| Opus 5.5 | $0.00017 | $0.01115 |
| Sonnet 5.5 | $0.00009 | $0.00557 |
| Haiku 4.5 | $0.00004 | $0.00279 |
Grade A, and why
testing 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Testing Framework
Unit Testing Strategy
For all custom code (themes and plugins), design and maintain tests using PHPUnit with the WordPress test framework (WP_UnitTestCase).
Test Coverage Targets
- Critical paths: 100% coverage (authentication, payment, data mutation)
- Business logic: 95%+ coverage
- Helper/utility functions: 90%+ coverage
- Template rendering: Integration tests for critical templates
- Overall target: As close to 100% as practical
Test Categories
tests/
├── unit/ # Pure unit tests (no WordPress dependencies)
│ ├── Validators/ # Input validation functions
│ ├── Formatters/ # Data formatting/transformation
│ └── Calculators/ # Business logic calculations
├── integration/ # Tests requiring WordPress (WP_UnitTestCase)
│ ├── PostTypes/ # Custom post type registration & behavior
│ ├── Taxonomies/ # Custom taxonomy behavior
│ ├── AJAX/ # AJAX handler tests
│ ├── REST/ # REST API endpoint tests
│ ├── Database/ # Custom table operations
│ ├── Hooks/ # Filter and action behavior
│ └── Admin/ # Admin page functionality
├── security/ # Security-specific tests
│ ├── Nonce/ # CSRF protection verification
│ ├── Capability/ # Authorization checks
│ ├── Sanitization/ # Input sanitization coverage
│ ├── Escaping/ # Output escaping coverage
│ └── SQLInjection/ # SQL injection resistance
├── performance/ # Performance regression tests
│ ├── QueryCount/ # Database query count assertions
│ ├── MemoryUsage/ # Memory consumption limits
│ └── ExecutionTime/ # Execution time thresholds
└── e2e/ # End-to-end tests (Cypress/Playwright)
├── Frontend/ # User-facing functionality
├── Admin/ # Dashboard functionality
└── Forms/ # Form submission flows
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 · 376 lines · 43 tokens per session scan A 6cd781163b20
testing is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (29 stars, last pushed 8mo ago), licensed MIT. It adds 43 tokens to every session and 2,787 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-08-30.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.