← Back to Scanner

test1 Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

test1 is an AI agent skill, created by chaunceyliu and published at openclaw/skills. ClawSecure audited test1 across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 55/100 (Medium Risk). The 4 findings concentrate in Command Injection, Policy Violation and Permissions Manifest, including Detects command injection patterns in agent skills: shell operators,... and Detects command injection patterns in agent skills: shell operators,.... 2 were rated high or critical severity.

Is test1 safe?

ClawSecure audited test1 and assigned a security score of 55/100 (Medium Risk), identifying 4 findings across Command Injection and Policy Violation. Review the findings below before installing.

What did ClawSecure find in test1?

ClawSecure identified 4 findings in test1, concentrated in Command Injection, Policy Violation and Permissions Manifest. 2 were rated high or critical severity. The most severe include Detects command injection patterns in agent skills: shell operators,... and Detects command injection patterns in agent skills: shell operators,....

How was test1 audited?

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

What does a score of 55 mean?

ClawSecure assigned test1 a security score of 55/100, placing it in the Medium Risk range. This reflects 4 findings led by Command Injection that warrant review before production use. 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 test1

ClawSecure detected 4 security findings in test1, spanning Command Injection, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for test1

Harden command execution
test1 constructs or runs system commands. Validate that commands are built only from trusted inputs, never pass user-controlled strings directly to a shell, and restrict execution to an allow-list of expected commands.
Resolve policy violations
test1 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.
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

Why Generic Scanners Fail at AI Agent SecurityUnderstanding Our 3-Layer Audit ProtocolOWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards

Related AI Agent Security Audits

keepScore 45/1002fccdde2f962fa7cScore 55/1007caf5d769dee89c3Score 55/1007caf5d769dee89c3Score 55/1002fccdde2f962fa7cScore 55/100

Scanned on February 7, 2026. test1 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