Caveat verdict

github-memory-sync

45
🟠 Risky
Significant risk patterns flagged — automated deep scan, not behavioral proof.

The skill explicitly backs up high-sensitivity files including USER.md and MEMORY.md to a GitHub repository via a personal access token, creating genuine risk of sensitive user data exposure if the repository is not strictly private.

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

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

30
security
60
transparency
70
maintenance

Permission integrity

Accesses agent memory/configuration files

agent_memory

Findings (4)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN="ghp_xxxxxxxxxxxxxxxxx

Pattern match high

apt-get install — installs system packages

CRON.md · code · apt-get install

Pattern match medium

References agent memory files

SKILL.md · frontmatter · MEMORY.md

Pattern match medium

Accesses OpenClaw config/secrets directly

SKILL.md · prose · downgraded · ~/.openclaw/openclaw.json

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class B/F). 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.

credential_accessagent_memory

Is this flag fair?

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