Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Security scanner for AI agent skills. Use BEFORE installing or running any new skill from ClawHub or external sources. Detects prompt injection, credential t...
Security scanner for AI agent skills. Use BEFORE installing or running any new skill from ClawHub or external sources. Detects prompt injection, credential t...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Scan AI agent skills for 35 categories of threats. v16 adds a 5-layer analysis pipeline, OWASP ASI projection mode, richer finding metadata, and Rust runtime evidence integration on top of the existing prompt injection, identity hijacking, memory poisoning, MCP poisoning, and supply chain coverage.
# Scan a skill directory npx -y @guava-parity/guard-scanner ./my-skills/ --verbose # Scan with identity protection npx -y @guava-parity/guard-scanner ./skills/ --soul-lock --strict # Filter to OWASP ASI mapped findings only npx -y @guava-parity/guard-scanner ./skills/ --compliance owasp-asi --format json # Installed CLI guard-scanner ./skills/ --strict # npm exec compatibility npm exec --yes --package=@guava-parity/guard-scanner -- guard-scanner ./skills/ --strict
guard-scanner <dir> # Scan directory guard-scanner <dir> -v # Verbose output guard-scanner <dir> --json # JSON report file guard-scanner <dir> --sarif # SARIF for CI/CD guard-scanner <dir> --html # HTML report guard-scanner <dir> --compliance owasp-asi --format json
Audit public registries for credential exposure. guard-scanner audit npm <username> guard-scanner audit github <username> guard-scanner audit clawhub <query> guard-scanner audit all <username> --verbose
Start as MCP server for IDE integration. guard-scanner serve Editor config (Cursor, Windsurf, Claude Code, OpenClaw): { "mcpServers": { "guard-scanner": { "command": "npx", "args": ["-y", "@guava-parity/guard-scanner", "serve"] } } } MCP tools: scan_skill, scan_text, check_tool_call, audit_assets, get_stats, and the async experimental task helpers.
Public quality contract: Benchmark corpus version: 2026-03-13.quality-v1 Precision target: >= 0.90 Recall target: >= 0.90 FPR/FNR budgets: <= 0.10 Explainability completeness: 1.0 Runtime policy latency budget: 5ms Evidence surfaces: docs/spec/capabilities.json docs/data/corpus-metrics.json docs/data/benchmark-ledger.json docs/data/fp-ledger.json
Monitor skill directories in real-time during development. guard-scanner watch ./skills/ --strict --soul-lock
Combine semantic detection with VirusTotal's 70+ antivirus engines. Optional โ guard-scanner works fully without it. export VT_API_KEY=your-key guard-scanner scan ./skills/ --vt-scan
The validated OpenClaw surface is the compiled runtime plugin entry (dist/openclaw-plugin.mjs) discovered through package.json > openclaw.extensions and mounted on before_tool_call for OpenClaw v2026.3.13, with regression coverage kept on v2026.3.8. The before_tool_call hook provides 27 runtime checks across 5 defense layers, while v16 scan output adds a second 5-layer analysis view: LayerFocus1. Threat DetectionReverse shell, curl|bash, SSRF2. Trust DefenseSOUL.md tampering, memory injection3. Safety JudgePrompt injection in tool arguments4. BehavioralNo-research execution detection5. Trust ExploitationAuthority claims, creator bypass Modes: monitor (log only), enforce (block CRITICAL, default), strict (block HIGH+).
Finding fields: layer, layer_name, owasp_asi, protocol_surface Compliance mode: --compliance owasp-asi MCP summaries: scan_skill, scan_text, and get_stats now surface layer and ASI context Runtime evidence: Rust memory_integrity and soul_hard_gate modules are represented in the TypeScript pipeline
FlagEffect--verbose / -vDetailed findings with line numbers--strictLower detection thresholds--soul-lockEnable identity protection patterns--json / --sarif / --htmlOutput format--fail-on-findingsExit 1 on findings (CI/CD)--check-depsScan package.json dependencies--rules <file>Load custom rules JSON--plugin <file>Load plugin module--compliance owasp-asiKeep only OWASP ASI mapped findings in output
module.exports = { name: 'my-plugin', patterns: [ { id: 'MY_01', cat: 'custom', regex: /dangerous_pattern/g, severity: 'HIGH', desc: 'Description', all: true } ] }; guard-scanner ./skills/ --plugin ./my-plugin.js
35 categories covering OWASP LLM Top 10 + Agentic Security Top 10. See src/patterns.ts for the full pattern database. Key categories: Prompt Injection โ hidden instructions, invisible Unicode, homoglyphs Identity Hijacking โฟ โ persona swap, SOUL.md overwrites, memory wipe Memory Poisoning โฟ โ crafted conversation injection MCP Security โ tool poisoning, SSRF, shadow servers A2A Contagion โ agent-to-agent worm propagation Supply Chain V2 โ typosquatting, slopsquatting, lifecycle scripts CVE Patterns โ CVE-2026-2256, 25046, 25253, 25905, 27825 โฟ = Requires --soul-lock flag
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.