← Back to Skills Marketplace
Security Monitor
by
chandrasekar-r
· GitHub ↗
· v1.0.0
8280
Downloads
6
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install security-monitor
Description
Real-time security monitoring for Clawdbot. Detects intrusions, unusual API calls, credential usage patterns, and alerts on breaches.
Usage Guidance
Install only if you are comfortable giving this skill access to host logs, process and port listings, Docker status, /root/clawd paths, and /root/clawd/skills/.env. Before use, remove or patch the .env content read, do not rely on --threats for scoping until fixed, run with the least privilege that still supports the checks you need, and protect or rotate the generated alert and state files.
Capability Analysis
Type: OpenClaw Skill
Name: security-monitor
Version: 1.0.0
The skill is classified as suspicious due to its use of high-risk capabilities, specifically reading sensitive files and executing system commands, even though these actions are ostensibly for security monitoring. The `scripts/monitor.cjs` file reads potentially sensitive `.env` files from `/root/clawd/` and executes commands like `tail`, `ss`, `ps aux`, and `docker ps` via `child_process.execSync`. While the script does not currently exfiltrate the *content* of credentials (only logging the *presence* of API keys), and a `TODO` comment for Telegram alerts is not implemented, the broad access to system information and sensitive files, combined with the ability to execute arbitrary commands, presents a significant risk if the code were to be modified or if the agent were compromised.
Capability Assessment
Purpose & Capability
Security log, port, process, file-change, and Docker checks fit a host security monitor, but scripts/monitor.cjs reads /root/clawd/skills/.env in full and only checks for provider-name strings rather than real credential-usage patterns.
Instruction Scope
SKILL.md advertises --threats for selecting monitored areas, but runChecks unconditionally runs every check, including credential-file inspection.
Install Mechanism
No package downloads, hidden installer, automatic service registration, or dependency setup are present; users run a local Node.js script manually or via PM2/systemd.
Credentials
Host log access, process and port inspection, Docker status, and /root/clawd paths are broadly privileged but mostly expected for monitoring; direct raw .env reading is under-scoped and not clearly disclosed.
Persistence & Privilege
Daemon mode and local alert/state files are disclosed and purpose-aligned, but the generated logs and state can contain sensitive security metadata and no retention or access-control guidance is provided.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install security-monitor - After installation, invoke the skill by name or use
/security-monitor - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: brute force detection, port anomaly monitoring, process monitoring, file change detection, Docker health checks
Metadata
Frequently Asked Questions
What is Security Monitor?
Real-time security monitoring for Clawdbot. Detects intrusions, unusual API calls, credential usage patterns, and alerts on breaches. It is an AI Agent Skill for Claude Code / OpenClaw, with 8280 downloads so far.
How do I install Security Monitor?
Run "/install security-monitor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Security Monitor free?
Yes, Security Monitor is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Security Monitor support?
Security Monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Security Monitor?
It is built and maintained by chandrasekar-r (@chandrasekar-r); the current version is v1.0.0.
More Skills