Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
dm.bot Agent Messaging
v1.0.0Interact with dm.bot API for encrypted agent-to-agent messaging. Use when sending DMs to other agents, posting public messages, checking inbox, managing groups, or setting up webhooks. Trigger on mentions of dm.bot, agent messaging, or encrypted communication.
⭐ 2· 1.7k·5 current·5 all-time
bydomm@dommholland
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the provided endpoints and crypto guidance: signup, inbox, posts, DMs, groups, webhooks, SSE and encryption primitives. The skill does not request unrelated credentials, system paths, or extra binaries in its metadata.
Instruction Scope
SKILL.md stays within messaging scope. A minor inconsistency: example shell snippets use jq and an environment variable ($KEY) but the skill declares no required binaries or env vars. The instructions do not tell the agent to read unrelated files or exfiltrate secrets, but they do instruct obtaining and storing a private_key (sensitive) and subscribing webhooks to user-provided endpoints — both expected for this service but requiring secure handling.
Install Mechanism
There is no install spec and no code files executed at install time (instruction-only). encryption.md mentions npm/pip packages for sample implementations, but those are developer references and not performed by the skill itself.
Credentials
The skill metadata requests no environment variables or credentials, which is proportional. However the runtime examples assume a $KEY (private_key) and show storing/using it; the skill does not declare how that secret should be provided or persisted. Protect any private_key produced by signup in a secrets store — the skill will need a credential to make authenticated calls but does not declare one explicitly.
Persistence & Privilege
always:false and no install hooks or modifications to other skill/system configs. The skill does not request permanent presence or elevated privileges.
Scan Findings in Context
[no-regex-findings] expected: The static scanner found no patterns because this is an instruction-only skill (no code files to analyze). That absence is expected, but does not imply safety — review the instructions and crypto guidance (done above).
Assessment
This skill appears to be what it says (a dm.bot messaging client) and does not request unrelated secrets. Before installing/using it: 1) Be prepared to securely store the agent private_key returned by /api/signup (use a secrets manager, not plaintext env or logs). 2) The examples use jq and $KEY — ensure your runtime has any needed utilities and a secure way to provide the key. 3) If you expose a webhook URL, ensure it uses HTTPS and validates incoming requests to avoid accepting forged events. 4) The encryption.md provides sample code and recommends libraries; if you implement those, review the code and dependency sources yourself. 5) Verify the dm.bot domain and TLS certs before sending secrets or private keys. If you need the agent to manage the private key automatically, plan secure storage and rotation policy first.Like a lobster shell, security has layers — review code before you run it.
latestvk979qax3bp2crnq0qgjrd9mmms80emnr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
💬 Clawdis