← Back to Scanner

memory-hygiene Security Audit Report

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

memory-hygiene is an AI agent skill, created by dylanbaker24 and published at openclaw/skills. ClawSecure audited memory-hygiene across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 4 findings concentrate in Policy Violation, Unauthorized Tool Use and Permissions Manifest, including Detects system manipulation, privilege escalation, and destructive file... and Attempts to access sensitive file: MEMORY.md. 2 were rated high or critical severity.

Is memory-hygiene safe?

ClawSecure audited memory-hygiene and assigned a security score of 75/100 (Medium Risk), identifying 4 findings across Policy Violation and Unauthorized Tool Use. Review the findings below before installing.

What did ClawSecure find in memory-hygiene?

ClawSecure identified 4 findings in memory-hygiene, concentrated in Policy Violation, Unauthorized Tool Use and Permissions Manifest. 2 were rated high or critical severity. The most severe include Detects system manipulation, privilege escalation, and destructive file... and Attempts to access sensitive file: MEMORY.md.

How was memory-hygiene audited?

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

What does a score of 75 mean?

ClawSecure assigned memory-hygiene a security score of 75/100, placing it in the Medium Risk range. This reflects 4 findings led by Policy Violation 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 memory-hygiene

ClawSecure detected 4 security findings in memory-hygiene, spanning Policy Violation, Unauthorized Tool Use, Permissions Manifest and Malicious Code.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for memory-hygiene

Resolve policy violations
memory-hygiene 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.
Audit external network connections
memory-hygiene 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.
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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

clawgo-upload-1.0.0Score 85/100clawgo-uploadScore 86/100clawgo-uploadScore 86/100clawgo-uploadScore 86/100clawgo-uploadScore 86/100

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