← Back to Scanner

mission-control Security Audit Report

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

mission-control is an AI agent skill, created by carlosazaustre and published at carlosazaustre/tenacitOS. ClawSecure audited mission-control across 93 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 5 findings concentrate in Malicious Code, Code Injection and Permissions Manifest, including Attempts to access sensitive file: SOUL.md and Attempts to access sensitive file: MEMORY.md. 4 were rated high or critical severity.

Is mission-control safe?

ClawSecure audited mission-control and assigned a security score of 55/100 (Medium Risk), identifying 5 findings across Malicious Code and Code Injection. Review the findings below before installing.

What did ClawSecure find in mission-control?

ClawSecure identified 5 findings in mission-control, concentrated in Malicious Code, Code Injection and Permissions Manifest. 4 were rated high or critical severity. The most severe include Attempts to access sensitive file: SOUL.md and Attempts to access sensitive file: MEMORY.md.

How was mission-control audited?

ClawSecure ran mission-control through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 93 files from carlosazaustre/tenacitOS.

What does a score of 55 mean?

ClawSecure assigned mission-control a security score of 55/100, placing it in the Medium Risk range. This reflects 5 findings led by Malicious Code 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 mission-control

ClawSecure detected 5 security findings in mission-control, spanning Malicious Code, Code Injection and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for mission-control

Audit external network connections
mission-control 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.
Eliminate dynamic code execution
mission-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.
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

ClawHavoc Explained: The Malware Family Targeting AI AgentsBeyond Static Scans: Why ClawSecure Verifies Agentic IntentWhy Generic Scanners Fail at AI Agent Security

Related AI Agent Security Audits

7caf5d769dee89c3Score 55/100ClawSecScore 45/1007caf5d769dee89c3Score 55/1007caf5d769dee89c3Score 55/1004f12f0da6eb7a565Score 55/100

Scanned on March 6, 2026. mission-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