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-toolkit-auditgit 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-toolkit-audit)<a href="https://agentmods.dev/skills/nvdigitalsolutions/mcp-ai-wpoos/mcp-ai-wpoos-toolkit-audit"><img src="https://agentmods.dev/badge/skills/nvdigitalsolutions/mcp-ai-wpoos/mcp-ai-wpoos-toolkit-audit/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-toolkit-audit"><img src="https://agentmods.dev/badge/skills/nvdigitalsolutions/mcp-ai-wpoos/mcp-ai-wpoos-toolkit-audit.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.00218 | $0.13865 |
| Opus 5.5 | $0.00087 | $0.05546 |
| Sonnet 5.5 | $0.00044 | $0.02773 |
| Haiku 4.5 | $0.00022 | $0.01387 |
Grade A, and why
mcp-ai-wpoos-toolkit-audit 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 4d 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.
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.
- 4d ago Changed · +58 lines · +49 tokens per session 861a26ce9d39
- 10d ago Changed · +1 lines a0c8b2ff23d9
- 15d ago First seen · 895 lines · 169 tokens per session scan A ddba1f7d95c1
mcp-ai-wpoos-toolkit-audit is a skill published in the GitHub repository nvdigitalsolutions/mcp-ai-wpoos (7 stars, last pushed today), with no licence file. It adds 218 tokens to every session and 13,865 once invoked, about $0.0009 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-10-06.
Other skills, from other repositories
omh-live-incident-response
This is an OMH live-incident-response workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
thinking-five-whys-plus
When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
thinking-map-territory
When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.
debug
Structured platform troubleshooting — classifies the problem layer, collects evidence, forms a root-cause hypothesis, and proposes a fix with validation and rollback steps.