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 nvdigitalsolutions/mcp-ai-wpoos --skill mcp-ai-wpoos-wporg-submissiongit clone --depth 1 https://github.com/nvdigitalsolutions/mcp-ai-wpoosWrote 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/nvdigitalsolutions/mcp-ai-wpoos/mcp-ai-wpoos-wporg-submission)<a href="https://agentmods.dev/skills/nvdigitalsolutions/mcp-ai-wpoos/mcp-ai-wpoos-wporg-submission"><img src="https://agentmods.dev/badge/skills/nvdigitalsolutions/mcp-ai-wpoos/mcp-ai-wpoos-wporg-submission/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/nvdigitalsolutions/mcp-ai-wpoos/mcp-ai-wpoos-wporg-submission"><img src="https://agentmods.dev/badge/skills/nvdigitalsolutions/mcp-ai-wpoos/mcp-ai-wpoos-wporg-submission.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.00207 | $0.13117 |
| Opus 5.5 | $0.00083 | $0.05247 |
| Sonnet 5.5 | $0.00041 | $0.02623 |
| Haiku 4.5 | $0.00021 | $0.01312 |
Grade C, and why
mcp-ai-wpoos-wporg-submission scanned grade C with 2 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 10d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
tracked files (and `rm -rf …/node_modules` there deletes it). To stage new Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
5. **Remote host disclosure (Guidelines 6/7)** — every `wp_remote_*`/curl The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 10d ago Changed · +175 lines · +56 tokens per session scan A → C 3bd5ca826772
- 20d ago Changed · +14 lines · +15 tokens per session 511be57a49fb
- 1mo ago Changed · +12 lines 169e7f98de1b
- 1mo ago Changed · +241 lines · -41 tokens per session f69b28274c13
- 1mo ago First seen · 274 lines · 177 tokens per session scan A 139532ccb6e6
mcp-ai-wpoos-wporg-submission is a skill published in the GitHub repository nvdigitalsolutions/mcp-ai-wpoos (7 stars, last pushed today), with no licence file. It adds 207 tokens to every session and 13,117 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.
Other skills, from other repositories
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
verification-quality
Truth scoring, code-quality verification, and automatic rollback with a high accuracy threshold. Use when validating agent output before it ships, gating changes on quality, or adding a verify-and-rollback safety loop.
test-e2e
End-to-end infrastructure pipeline validation across Terraform and Ansible repos.
ci-test-optimization
A guide for analysing and preparing improvements to a CI test pipeline. CI, or continuous integration, automatically builds and tests code changes as they are submitted.
everr-use-telemetry
Use when investigating production or local behavior with logs, traces, metrics, errors, crashes, slow requests, flaky tests, regressions, missing behavior, stale telemetry, user reports, incidents, or questions that real runtime data can answer.
everr-working-with-ci
Use when a task mentions CI, GitHub Actions, workflow runs, checks, jobs, steps, logs, build or test failures, flaky or slow CI, PR status, branch status, release pipelines, or whether a commit is green.