ave vs hol-guard
ave: AVE (Agentic Vulnerability Enumeration) is a behavioral classification standard for agentic AI components, addressing the gap in existing vulnerability standards for AI-specific threats. It provides stable IDs, AIVSS scores, and maps findings to established security frameworks like OWASP MCP and MITRE ATLAS.; hol-guard: HOL Guard acts as an antivirus for AI harnesses, intercepting tool actions to protect against file changes and network contact. It also includes `plugin-scanner`, a complementary tool for linting and verifying AI plugins and packages in CI environments before release, ensuring quality and security.
TL;DR
Scanning agent skill files for prompt injection and other AI-specific vulnerabilities
- You run Codex, Claude Code, Copilot CLI, Cursor or similar and want a check before new or changed tools run.
- You maintain plugins, skills or MCP servers and want a CI step such as `plugin-scanner verify .`.
- You want local receipts of what was approved or blocked.
- You need a clear licence in GitHub's metadata today; our data shows none detected.
- You want a minimal tool: the README covers a large surface of commands and integrations.
- You cannot accept extra approval prompts in your agent workflow.
Side-by-Side Comparison
avehol-guardFeatures
avehol-guardUse Cases
avehol-guardBest For
avehol-guardFAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.