openclaw-daily-ops@1.0.0
CAUTION· static onlyPublisher claims: "Daily cost reporting + session hygiene for OpenClaw deployments. Tracks per-session API spend, shows 7-day trend, and wipes zombie sessions >24h old to preve..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-16 and scored it 61/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Context shift attempt; Prompt injection; Authorization escalation language. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
1. Enable Developer Mode in Discord (Settings → Advanced → Developer Mode)Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Execute `scripts/cost_report.py --config /path/to/config.json` and capture output.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Yes. Run the setup on each machine with its own `config.json`. Both can post to the same Discord webhook.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.1. Enable Developer Mode in Discord (Settings → Advanced → Developer Mode)Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.1. Enable Developer Mode in Discord (Settings → Advanced → Developer Mode)Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Two tasks in one nightly cron: **know what you spent, kill what's dead.**Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."discord_webhook": "https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN",Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."discord_webhook": "https://discord.com/api/webhooks/YOUR/WEBHOOK",Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Execute `scripts/zombie_killer.py --config /path/to/config.json` and capture output.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
19 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zylcold: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Discord webhook URL≈ +4 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.