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 SolveaCX/voc-mcp --skill voc-openapigit clone --depth 1 https://github.com/SolveaCX/voc-mcpWrote 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/solveacx/voc-mcp/voc-openapi)<a href="https://agentmods.dev/skills/solveacx/voc-mcp/voc-openapi"><img src="https://agentmods.dev/badge/skills/solveacx/voc-mcp/voc-openapi/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/solveacx/voc-mcp/voc-openapi"><img src="https://agentmods.dev/badge/skills/solveacx/voc-mcp/voc-openapi.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.00065 | $0.00274 |
| Opus 5 | $0.00032 | $0.00137 |
| Sonnet 5 | $0.00013 | $0.00055 |
| Haiku 4.5 | $0.00006 | $0.00027 |
Grade A, and why
voc-openapi 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 9d 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.
What it actually says
VOC OpenAPI Query Rules
- First identify the platform, data type, and action specified by the user, such as searching content, getting details, querying comments, or finding profiles.
- Check the
voc-openapiMCP for platform tools whose names and descriptions match the request, and prefer read-only tools. - When there are many tools, search by "platform name + action", such as
Threads + search recentorReddit + comments. - Do not switch directly to a browser just because the target tool is not visible in the first screen of results; complete the MCP tool lookup first.
- After calling a tool, organize the body text, author, publish time, engagement data, pagination information, and original links according to the user's needs. Do not invent missing fields.
- Use a browser only when VOC OpenAPI has no matching capability, the tool call fails and cannot be recovered, or the user explicitly asks to view or operate a web page.
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.
- 9d ago First seen · 14 lines · 65 tokens per session scan A 5acd007f66b4
voc-openapi is a skill published in the GitHub repository SolveaCX/voc-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 274 once invoked, about $0.0003 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, then fills the gaps with list (filters, sort, a time…
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.