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.
git clone --depth 1 https://github.com/vargHQ/skillsWrote 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/mcp/varghq/skills/varg-how-to)<a href="https://agentmods.dev/mcp/varghq/skills/varg-how-to"><img src="https://agentmods.dev/badge/mcp/varghq/skills/varg-how-to/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/mcp/varghq/skills/varg-how-to"><img src="https://agentmods.dev/badge/mcp/varghq/skills/varg-how-to.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
varg-how-to 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 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.
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
{
"varg-how-to": {
"type": "http",
"url": "https://api.varg.ai/v2/skills/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own 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.
- 10d ago First seen · 6 lines scan A 78ce0ac22fce
varg-how-to is an MCP server published in the GitHub repository vargHQ/skills (24 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-29.
varg-how-to compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| varg-how-tovargHQ/skills | MCP server | 24 | 2d ago | MIT | A | — | Claude Code |
| mcp-seedanceAceDataCloud/SeedanceMCP | MCP server | 21 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| seedanceAceDataCloud/SeedanceMCP | MCP server | 21 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcp-veoAceDataCloud/VeoMCP | MCP server | 3 | 7d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcp-klingAceDataCloud/KlingMCP | MCP server | 1 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcp-wanAceDataCloud/WanMCP | MCP server | 1 | 7d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcp-hailuoAceDataCloud/HailuoMCP | MCP server | 1 | 7d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |