SkillAgentSearch skills...

openclaw-deployment-hardening

Secure OpenClaw deployments with preflight hardening checks, CI/CD guardrails, container runtime restrictions, and post-deploy verification

Install / Use

npx skills add BagelHole/DevOps-Security-Agent-Skills --skill openclaw-deployment-hardening

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Category

Security

Supported Platforms

Universal

Our assessment of openclaw-deployment-hardening

openclaw-deployment-hardening scores 82/100 on our quality scale, 965th of 1,111 Security skills we index.

Its SKILL.md is 3.2 KB long, well organised into 10 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,113 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 6 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

openclaw-deployment-hardening compared with similar skills

All 4 of these similar skills score higher than openclaw-deployment-hardening; compare them before choosing.

SkillScoreStarsUpdatedFormat
openclaw-deployment-hardening (this skill)by BagelHole821.1k6mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install openclaw-deployment-hardening?
Run npx skills add BagelHole/DevOps-Security-Agent-Skills --skill openclaw-deployment-hardening. The install tabs above show the steps for each supported agent.
Which AI agents does openclaw-deployment-hardening work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is openclaw-deployment-hardening safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is openclaw-deployment-hardening still maintained?
The repository was last updated about 6 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: openclaw-deployment-hardening description: Secure OpenClaw deployments with preflight hardening checks, CI/CD guardrails, container runtime restrictions, and post-deploy verification. Use when shipping OpenClaw with Docker, Kubernetes, or automated release pipelines. license: MIT metadata: author: devops-skills version: "1.0"

OpenClaw Deployment Hardening

Use this skill to add repeatable security gates around OpenClaw build and deployment workflows.

Enforce a Secure Build Pipeline

Add mandatory controls to CI before artifacts are promoted:

  1. Dependency and lockfile vulnerability scan (fail on critical CVEs).
  2. Image scan for OS/package vulnerabilities.
  3. Secret scanning across source and build context.
  4. SBOM generation and artifact signing.
  5. Policy check that blocks deploy when controls fail.

Example CI step order:

# Build
npm ci
npm run build

# Security gates
trivy fs .
trivy image my-registry/openclaw:${GIT_SHA}
syft my-registry/openclaw:${GIT_SHA} -o spdx-json > sbom.json
cosign sign --key cosign.key my-registry/openclaw:${GIT_SHA}

Lock Down Container Runtime

Run OpenClaw with restrictive defaults:

  • Non-root user in container
  • Read-only root filesystem where possible
  • Drop all Linux capabilities, add back only required
  • no-new-privileges enabled
  • Constrained CPU/memory limits to reduce abuse impact
  • Seccomp/AppArmor (or equivalent) profile enforced

Kubernetes-oriented expectations:

  • runAsNonRoot: true
  • allowPrivilegeEscalation: false
  • readOnlyRootFilesystem: true
  • network policy deny-all baseline with explicit allow rules

Gate Production Promotion

Require explicit promotion checks:

  • Security sign-off on CVE exceptions.
  • Signed artifact verification in deployment stage.
  • Drift check between expected and live manifest values.
  • Deployment only from immutable tags or digests.

Avoid mutable latest tags for production OpenClaw services.

Protect Data and Session Surfaces

  • Minimize prompt/response retention by policy.
  • Mask secrets and PII in logs before shipping to SIEM.
  • Encrypt persistent volumes and backups.
  • Isolate tenant/session data boundaries when serving multiple teams.

Post-Deploy Verification

Run a hardening smoke test immediately after rollout:

kubectl get pods -n openclaw
kubectl auth can-i --as=system:serviceaccount:openclaw:default list secrets -n openclaw
kubectl get networkpolicy -n openclaw
kubectl logs deploy/openclaw -n openclaw --tail=200

Verify:

  • Pod security context matches policy.
  • Service account permissions are least privilege.
  • Ingress auth/rate limits are effective.
  • No plaintext secrets appear in logs.

Incident-Ready Rollback Pattern

Maintain a hardened rollback workflow:

  1. Freeze further rollouts.
  2. Revoke suspect tokens and rotate secrets.
  3. Roll back to last signed known-good image digest.
  4. Re-run post-deploy hardening verification.
  5. Capture timeline and artifacts for forensics.

Related Skills

Related Skills

View on GitHub
GitHub Stars1.1k
CategorySecurity
Updated5mo ago
Forks158

Languages

Shell

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info