← Back to Scanner

"security-best-practices" Security Audit Report

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

"security-best-practices" is an AI agent skill, created by openai and published at openai/skills. ClawSecure audited "security-best-practices" across 13 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 15/100 (High Risk). The 10 findings concentrate in Code Injection, Permissions Manifest and Policy Violation, including Potentially dangerous code pattern detected: exec\( and Potentially dangerous code pattern detected: eval\(. 8 were rated high or critical severity.

Is "security-best-practices" safe?

ClawSecure audited "security-best-practices" and assigned a security score of 15/100 (High Risk), identifying 10 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in "security-best-practices"?

ClawSecure identified 10 findings in "security-best-practices", concentrated in Code Injection, Permissions Manifest and Policy Violation. 8 were rated high or critical severity. The most severe include Potentially dangerous code pattern detected: exec\( and Potentially dangerous code pattern detected: eval\(.

How was "security-best-practices" audited?

ClawSecure ran "security-best-practices" through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 13 files from openai/skills.

What does a score of 15 mean?

ClawSecure assigned "security-best-practices" a security score of 15/100, placing it in the High Risk range. This is driven by 10 findings led by Code Injection that should be addressed before 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 "security-best-practices"

ClawSecure detected 10 security findings in "security-best-practices", spanning Code Injection, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for "security-best-practices"

Eliminate dynamic code execution
"security-best-practices" evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
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.
Resolve policy violations
"security-best-practices" trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.

Related Security Research

Why Generic Scanners Fail at AI Agent SecurityBeyond Static Scans: Why ClawSecure Verifies Agentic Intent

Related AI Agent Security Audits

@martian-engineering/lossless-clawScore 25/100@martian-engineering/lossless-clawScore 25/100openclaw-dashboard-repoScore 25/100openclaw-dashboard-repoScore 25/100openclaw-dashboard-repoScore 25/100

Scanned on March 5, 2026. "security-best-practices" 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