← Back to Scanner

coding-agent Security Audit Report

πŸ”­ Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

coding-agent is an AI agent skill, created by steipete and published at openclaw/skills. ClawSecure audited coding-agent across 2 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 Unauthorized Tool Use, Permissions Manifest and Policy Violation, including Detects system manipulation, privilege escalation, and… and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is coding-agent safe?

ClawSecure audited coding-agent and assigned a security score of 85/100 (Safe), identifying 3 findings across Unauthorized Tool Use and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in coding-agent?

ClawSecure identified 3 findings in coding-agent, concentrated in Unauthorized Tool Use, Permissions Manifest and Policy Violation. 1 was rated high or critical severity. The most severe include Detects system manipulation, privilege escalation, and… and Missing config.json - agent may not be properly configured.

How was coding-agent audited?

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

What does a score of 85 mean?

ClawSecure assigned coding-agent 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 coding-agent

ClawSecure detected 3 security findings in coding-agent, spanning Unauthorized Tool Use, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for coding-agent

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
coding-agent trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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

How to Secure an MCP Server: The 2026 Guide→What Is MCP Security? Model Context Protocol Explained→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

devops-mainScore 75/100TestFilesScore 95/100devops-mainScore 75/100devops-mainScore 75/100redditScore 80/100

Scanned on February 26, 2026. coding-agent 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