Skip to content
TakoAPI
Back to skills

security-operator

by kevjade

Coding Agents & IDEs
556Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Runtime security guardrails for OpenClaw agents.

Description

What This Skill Does

Runtime security guardrails for OpenClaw agents covering prompt injection, credential leaks, cost runaway, and cascade failures. Two operating modes separate browsing from autonomous execution, each with distinct trust boundaries. Includes a one-time setup wizard, credential audit commands, and community skill vetting workflows.

Guardrails are behavioral rather than tool-based, adding zero token overhead during normal operation while still blocking high-risk actions.

When to Use It

  • Block prompt injection attempts embedded in untrusted web content during research tasks
  • Audit OpenClaw config files for plaintext API keys or misconfigured .env permissions
  • Vet a community skill from ClawHub before installing it in a production workspace
  • Enforce explicit approval gates before destructive actions like force pushes or credential exports
  • Schedule a weekly automated security health check via cron

Example Workflow

INPUT

User asks: Run the security setup wizard for my OpenClaw workspace

AGENT
  1. 1

    Run openclaw security audit --deep to assess current security posture

  2. 2

    Apply safe defaults with openclaw security audit --fix

  3. 3

    Verify spending limits are configured in the gateway or provider dashboard

  4. 4

    Check that logging is enabled and logs are being written to the expected path

  5. 5

    Ask user for approval, then append always-on guardrails to AGENTS.md

OUTPUT

Security guardrails written to AGENTS.md, safe defaults applied, and optional weekly audit cron offered

Installation

clawhub install kevjade/security-operator

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links