Does a scanner prove an agent skill is safe?
No. Scanner output is a trust signal, not a certification. Skills touching customer data, production systems, or external accounts still need human review and guardrails.
Comparison
Agent skills can automate powerful actions. Review manifests, scripts, permissions, dependencies, and source before trusting them.
Skill review should focus on what the package can access and what code it can execute.
| Tool | Free / no cost | No signup | Manifest review | Secret scanning | Dep. CVEs | SAST / code patterns | Skill trust report | Notes |
|---|---|---|---|---|---|---|---|---|
| CyberLens AI | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | Purpose-built for OpenClaw, Kimi CLAW, and agentic workflow trust decisions |
| Manual code review | ✓ | ✓ | ✓ | – | – | – | ✓ | Time-intensive; requires developer expertise |
| Semgrep | ✓ | ✓ | – | ✓ | – | ✓ | – | OSS CLI; no skill-specific trust scoring |
| Trivy | ✓ | ✓ | – | ✓ | ✓ | – | – | Container/repo focused; no manifest analysis |
| GitHub CodeQL / GHAS | – | – | – | ✓ | ✓ | ✓ | – | Free for public repos only; no skill-specific output |
| npm / pkg provenance | ✓ | ✓ | – | – | ✓ | – | – | Package provenance verification only |
No. Scanner output is a trust signal, not a certification. Skills touching customer data, production systems, or external accounts still need human review and guardrails.
CyberLens AI guidance is informed by established security standards and public vulnerability intelligence.