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 courtneyr-dev/wp-release-audit-method --skill wordpress-audit-handoffgit clone --depth 1 https://github.com/courtneyr-dev/wp-release-audit-methodWrote 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/courtneyr-dev/wp-release-audit-method/wordpress-audit-handoff)<a href="https://agentmods.dev/skills/courtneyr-dev/wp-release-audit-method/wordpress-audit-handoff"><img src="https://agentmods.dev/badge/skills/courtneyr-dev/wp-release-audit-method/wordpress-audit-handoff.svg" alt="Measured on agentmods" 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.00084 | $0.04047 |
| Opus 5 | $0.00042 | $0.02024 |
| Sonnet 5 | $0.00017 | $0.00809 |
| Haiku 4.5 | $0.00008 | $0.00405 |
Grade A, and why
wordpress-audit-handoff scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`gh repo view <owner>/<repo> --json isPrivate` (or an anonymous `curl` → expect 200, not 404). The source is not reproduced here
Licensed GPL-2.0
The repository is licensed GPL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 8d ago First seen · 290 lines · 84 tokens per session scan A 3bbbc0c80922
wordpress-audit-handoff is a skill published in the GitHub repository courtneyr-dev/wp-release-audit-method (9 stars, last pushed 2d ago), licensed GPL-2.0. It adds 84 tokens to every session and 4,047 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
loop-verifier
Independent verification agent for loop-produced changes. Finds reasons to reject. Runs tests. Confirms diff scope. Use after minimal-fix or any implementer sub-agent — never in the same role as the implementer.
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.