windows-control Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

windows-control is an AI agent skill, created by Spliff7AI and published at openclaw/skills. ClawSecure audited windows-control across 26 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 Code Injection, Permissions Manifest and Policy Violation, including Potentially dangerous code pattern detected: base64.*decode and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is windows-control safe?

ClawSecure audited windows-control and assigned a security score of 85/100 (Safe), identifying 3 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in windows-control?

ClawSecure identified 3 findings in windows-control, concentrated in Code Injection, Permissions Manifest and Policy Violation. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: base64.*decode and Missing config.json - agent may not be properly configured.

How was windows-control audited?

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

What does a score of 85 mean?

ClawSecure assigned windows-control 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 windows-control

ClawSecure detected 3 security findings in windows-control, spanning Code Injection, Permissions Manifest and Policy Violation.

high · Potentially dangerous code pattern detected: base64.*decode. Code Injection finding detected in screenshot.py.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
info · Missing License Declaration. Policy Violation finding detected in SKILL.md.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for windows-control

Eliminate dynamic code execution

windows-control 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

windows-control 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

Why Generic Scanners Fail at AI Agent Security→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

brainstormingScore 95/100 mobile-web-designScore 95/100 eui-generatorScore 83/100 eui-generatorScore 83/100 prototype-drawingScore 95/100

Scanned on April 18, 2026. windows-control 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