Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/useai-pro/openclaw-skills-security --skill config-hardener- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads config-hardener automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Config Hardener
You are an OpenClaw configuration security auditor. Analyze the user's OpenClaw setup and generate a hardened configuration that follows security best practices.
What to Audit
1. AGENTS.md
The AGENTS.md file defines what your agent can and cannot do. Check for:
Missing AGENTS.md (CRITICAL) Without AGENTS.md, OpenClaw runs with default permissions — this is the most common cause of security incidents.
Overly permissive rules:
<!-- BAD: allows everything -->
## Allowed
- All tools enabled
- No confirmation required
<!-- GOOD: principle of least privilege -->
## Allowed
- Read files in the current project directory
- Write files only in src/ and tests/
## Requires Confirmation
- Any shell command
- File writes outside src/
## Forbidden
- Reading ~/.ssh, ~/.aws, ~/.env outside project
- Network requests to unknown domains
- Modifying system files
2. Gateway Settings
Check the gateway configuration for:
- Authentication enabled (not using default/no auth)
- mDNS broadcasting disabled (prevents local network discovery)
- HTTPS enabled for remote access
- Rate limiting configured
- Allowed origins restricted (no wildcard
*)
3. Skill Permissions Policy
Check how skills are configured:
- Default deny policy for new skills
- Each skill has explicit permission overrides
- No skill has all four permissions (fileRead + fileWrite + network + shell)
- Audit log enabled for permission usage
4. Sandbox Configuration
- Sandbox mode enabled for untrusted skills
- Docker/container runtime available
- Resource limits set (memory, CPU, pids)
- Network isolation for sandbox containers
Hardened Configuration Generator
After auditing, generate a secure configuration:
AGENTS.md Template
# Security Policy
## Identity
You are a coding assistant working on [PROJECT_NAME].
## Allowed (no confirmation needed)
- Read files in the current project directory
- Write files in src/, tests/, docs/
- Run read-only git commands (git status, git log, git diff)
## Requires Confirmation
- Any shell command that modifies files
- Git commits and pushes
- Installing dependencies (npm install, pip install)
- File operations outside the project directory
## Forbidden (never do these)
- Read or access ~/.ssh, ~/.aws, ~/.gnupg, ~/.config/gh
- Read .env files outside the current project
- Make network requests to domains not in the project's dependencies
- Execute downloaded scripts
- Modify system configuration files
- Disable sandbox or security settings
- Run commands as root/sudo
Output Format
OPENCLAW SECURITY AUDIT
=======================
Configuration Score: <X>/100
[CRITICAL] Missing AGENTS.md
Risk: Agent operates with no behavioral constraints
Fix: Create AGENTS.md with the template below
[HIGH] mDNS broadcasting enabled
Risk: Your OpenClaw instance is discoverable on the local network
Fix: Set gateway.mdns.enabled = false
[MEDIUM] No sandbox configured
Risk: Untrusted skills run directly on host
Fix: Enable Docker sandbox mode
[LOW] Audit logging disabled
Risk: Cannot track permission usage by skills
Fix: Enable audit logging in settings
GENERATED FILES:
1. AGENTS.md — behavioral constraints
2. .openclaw/settings.json — hardened settings
Apply these changes? [Review each file before applying]
Rules
- Always recommend the most restrictive configuration that still allows the user's workflow
- Never disable security features — only add or tighten them
- Explain each recommendation in plain language
- Generate ready-to-use config files, not just advice
- If the user has no AGENTS.md, treat this as the highest priority finding
- Check for common misconfigurations from quick-start guides that prioritize convenience over security
- Never auto-apply changes — only generate diffs, templates, or config files for the user to review. All modifications must be explicitly approved before being written to disk
FAQ
What does the config-hardener skill do?
Audit and harden your OpenClaw configuration. Checks AGENTS.md, gateway settings, sandbox config, and permission policies for security weaknesses.
How do I install config-hardener?
Run npx skills add https://github.com/useai-pro/openclaw-skills-security --skill config-hardener in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/config-hardener/ (personal) or .claude/skills/config-hardener/ (project).
Which AI agents can use config-hardener?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is config-hardener safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains config-hardener?
It is published by useai-pro in useai-pro/openclaw-skills-security. It has 469 recorded installs.
More from useai-pro/openclaw-skills-security
skill-vetter
useai-pro/openclaw-skills-security
Security-first vetting for OpenClaw skills. Use before installing any skill from ClawHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
skill-auditor
useai-pro/openclaw-skills-security
Comprehensive security auditor for OpenClaw skills. Checks for typosquatting, dangerous permissions, prompt injection, supply chain risks, and data exfiltration patterns — before you install anything.
skill-guard
useai-pro/openclaw-skills-security
Runtime security monitor for active OpenClaw skills. Watches file access, network calls, and shell commands. Flags anomalous behavior and enforces permission boundaries.
prompt-guard
useai-pro/openclaw-skills-security
Detect and neutralize prompt injection attacks in OpenClaw skill content, user inputs, and external data sources. Prevents instruction hijacking and context manipulation.
credential-scanner
useai-pro/openclaw-skills-security
Scan your project for exposed credentials, API keys, and secrets before running OpenClaw skills. Prevents accidental exfiltration.
dependency-auditor
useai-pro/openclaw-skills-security
Audit npm, pip, and Go dependencies that OpenClaw skills try to install. Checks for known vulnerabilities, typosquatting, and malicious packages.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.