ClawAudit verdict

memory-manager-secure

🟢 Trusted

Low risk — reviewed by ClawAudit, behavior matches stated purpose

MEMORY.md auto-management skill reading OpenClaw config and sending session data to user-configured LLM providers; explicitly documents what data is sent and to whom with local fallback mode.

⚠ 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.

security

transparency

maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Accesses agent memory/configuration files

agent_memory

Findings (4)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY="your-api-key-here

Pattern match high

Accesses OpenClaw config/secrets directly

SKILL.md · code · ~/.openclaw/openclaw.json

Pattern match medium

References agent memory files

SKILL.md · code · MEMORY.md

Pattern match low

Python urllib.request — network access

scripts/update-memory.sh · prose · downgraded · urllib.request

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_memorycredential_access

Is this flag fair?

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