ClawAudit verdict

triple-layer-memory

88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose

Three-layer memory management system using local files and Mem0 for cross-session recall; agent_memory capability is used as intended for memory management, no external data exfiltration.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

40
security
70
transparency
80
maintenance

Permission integrity

Accesses agent memory/configuration files

agent_memory

Findings (4)

Pattern match high

References SSH/GPG private keys

docs/github-upload-guide.md · code · ssh-key

Pattern match high

Accesses .ssh directory

docs/github-upload-guide.md · code · .ssh/

Pattern match medium

References agent memory files

SKILL.md · code · MEMORY.md

Pattern match medium

Accesses OpenClaw config/secrets directly

scripts/memory_consistency.py · prose · downgraded · ~/.openclaw/openclaw.json

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

agent_memory

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API