neo Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

neo is an AI agent skill, created by brucko and published at openclaw/skills. ClawSecure audited neo across 57 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 3 findings concentrate in Policy Violation, Permissions Manifest and Malicious Code, including Attempts to access sensitive file: SOUL.md and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is neo safe?

ClawSecure audited neo and assigned a security score of 85/100 (Safe), identifying 3 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in neo?

ClawSecure identified 3 findings in neo, concentrated in Policy Violation, Permissions Manifest and Malicious Code. 1 was rated high or critical severity. The most severe include Attempts to access sensitive file: SOUL.md and Missing config.json - agent may not be properly configured.

How was neo audited?

ClawSecure ran neo through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 57 files from openclaw/skills.

What does a score of 85 mean?

ClawSecure assigned neo a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for neo

ClawSecure detected 3 security findings in neo, spanning Policy Violation, Permissions Manifest and Malicious Code.

high · Attempts to access sensitive file: SOUL.md. Malicious Code finding detected in game-theorist.md.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
info · Skill manifest does not include a 'license' field. Specifying a license.... Policy Violation finding detected in SKILL.md.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for neo

Resolve policy violations

neo trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.

Add a config.json permissions manifest

A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.

Audit external network connections

neo connects to external endpoints. Verify every outbound connection goes to a trusted destination. Unauthorized callbacks are a primary indicator of ClawHavoc malware and data exfiltration. ClawSecure's proprietary engine monitors for known malicious endpoints including C2 infrastructure.

Pin dependencies to exact versions

Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

clawdhubScore 75/100 b4abd97bcb77151aScore 75/100 mission-controlScore 83/100 c1cb277f8f4aa143Score 95/100 19af8eafb16b72f6Score 75/100

Scanned on February 7, 2026. neo is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan