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 agentmods add mcp/dennysoliveira/wow-addon-dev/spec-workflowgit clone --depth 1 https://github.com/DennysOliveira/wow-addon-devWrote 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/dennysoliveira/wow-addon-dev/spec-workflow)<a href="https://agentmods.dev/mcp/dennysoliveira/wow-addon-dev/spec-workflow"><img src="https://agentmods.dev/badge/mcp/dennysoliveira/wow-addon-dev/spec-workflow.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
spec-workflow 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 3d 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
{
"spec-workflow": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@pimzino/spec-workflow-mcp@latest",
"."
]
}
}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.
- 3d ago First seen · 12 lines scan A 855a6845ad93
spec-workflow is an MCP server published in the GitHub repository DennysOliveira/wow-addon-dev (12 stars, last pushed 5mo 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-08-30.
Other mcp servers, from other repositories
fff
MCP server "fff" as configured in dmtrKovalenko/fff. Launched with ./target/release/fff-mcp.
hated-wow-mcp
MCP server for World of Warcraft addon development — 20 tools giving Claude, Cursor and any MCP client the in-game Lua API, Blizzard's shipped UI source, CVars, FileDataIDs and texture atlases, plus Lua linting, TOC/XML validation and addon scaffolding. R. Runs locally from the hated-wow-mcp npm package.
mlua-swarm
MCP server "mlua-swarm" as configured in ynishi/mlua-swarm. Runs in Docker (ghcr.io/ynishi/mse:0.9.2).
memscope-mcp
AI-native memory research MCP server for reverse engineering. Runs locally from the memscope-mcp Python package.
umbrella-runtime-mcp
MCP server "umbrella-runtime-mcp" as configured in madonchik123/umbrella-mcp. Runs locally from the umbrella-runtime-mcp Python package.
gmod-mcp
MCP tool for Garry's Mod: RCON, Lua execution, window screenshot/control, and SFTP file management. Runs locally from the gmod-mcp npm package.