Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/jnmetacode/shellward/security-guidenpx skills add jnMetaCode/shellward --skill security-guidegit clone --depth 1 https://github.com/jnMetaCode/shellwardWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00023 | $0.00628 |
| Opus 5 | $0.00012 | $0.00314 |
| Sonnet 5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade B, and why
security-guide scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Suggest `chmod 600 ~/.env ~/.ssh/* ~/.aws/credentials` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- Suggest `chmod 600 ~/.env ~/.ssh/* ~/.aws/credentials` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShellWard Security Deployment Guide / 安全部署指南
When the user invokes this skill, provide a complete security deployment checklist based on the following best practices. Check the current system state using available tools and give actionable recommendations.
Security Checklist
1. Network Control / 网络控制
- Check if OpenClaw gateway port (19000/19001) is exposed to public network
- Recommend binding to 127.0.0.1 or using a reverse proxy with authentication
- Suggest firewall rules:
ufw allow from 127.0.0.1 to any port 19000 - For cloud servers: check security group rules
2. Container Isolation / 容器隔离
- Recommend running OpenClaw in Docker with restricted capabilities:
docker run --cap-drop=ALL --cap-add=NET_BIND_SERVICE \ --read-only --tmpfs /tmp \ -u 1000:1000 \ openclaw - Suggest resource limits:
--memory=2g --cpus=1 - Mount only necessary directories
3. Credential Management / 凭证管理
- Scan for plaintext secrets in .env, .bashrc, environment variables
- Recommend using a secret manager (Vault, doppler, etc.)
- Check file permissions on sensitive files (should be 0600)
- Suggest
chmod 600 ~/.env ~/.ssh/* ~/.aws/credentials
4. Audit Logging / 审计日志
- Verify ShellWard audit log is active at ~/.openclaw/shellward/audit.jsonl
- Show recent security events
- Recommend log rotation and backup strategy
- Suggest sending critical events to external SIEM
5. Plugin Security / 插件安全
- List all installed plugins and check for known risks
- Disable auto-update for plugins
- Only install from trusted sources
- Scan plugin code for suspicious patterns
6. Patch Management / 补丁管理
- Check current OpenClaw version
- Report known vulnerabilities for current version
- Recommend upgrade path
- Check Node.js version (must be >= 22.12)
Available Commands
Remind the user about ShellWard's quick commands:
/security— Full security status overview/audit [count] [filter]— View audit log/harden— Scan for issues,/harden fixto auto-fix/scan-plugins— Scan plugins for security risks/check-updates— Check versions and vulnerabilities
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 69 lines · 23 tokens per session scan B 5f5098b6d3c0
security-guide is a skill published in the GitHub repository jnMetaCode/shellward (130 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 628 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
safe-helper
A benign skill that provides helpful text utilities.
violation-skill
A skill whose code violates the plugin-level policy manifest.
evil-codex-skill
A malicious Codex skill that exfiltrates data.
safe-codex-skill
A benign Codex skill for testing — no risky patterns.
evil-cursor-skill
Malicious skill that steals credentials from the workspace.
safe-cursor-skill
A benign Cursor skill for formatting code.