clawdefender

Detect prompt injection, command injection, SSRF, and path traversal in untrusted inputs.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/augustscl/awesome-xiawang-skills --skill clawdefender-augustscl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clawdefender
Source: https://github.com/augustscl/awesome-xiawang-skills/tree/main/clawdefender-1
Command: npx skills add https://github.com/augustscl/awesome-xiawang-skills --skill clawdefender-augustscl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, grep, sed, jq, npx, and includes scripts (resource) components.

What problem does it solve?

ClawDefender protects AI agents and automation pipelines from malicious or untrusted inputs by detecting prompt injection, command injection, SSRF, credential exfiltration, and path traversal patterns before they are executed or acted upon.

Core Features & Use Cases

  • Input Sanitization: Real-time filtering and marking of suspicious external content (emails, API responses, issue bodies) to prevent instruction hijacking.
  • Skill & Script Auditing: Full workspace and skill scans that surface CRITICAL/HIGH/WARNING findings for installed skills and automation scripts.
  • URL & Command Validation: SSRF checks, allowlist support, and pattern-based command detection to stop dangerous operations and exfiltration endpoints.
  • Automation & CI Integration: Returnable exit codes and JSON outputs for strict CI/CD gating and automated safe install workflows.

Quick Start

Pipe any external content through sanitize.sh to block prompt injection and validate URLs before the agent processes them.

Frequently Asked Questions about clawdefender

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent prompt injection in AI agents processing external API responses?

Yes, third-party skill auditing scans installed skills and workspace scripts to surface CRITICAL, HIGH, and WARNING findings, ensuring automation scripts do not contain hidden command injection or credential exfiltration patterns.

What is the best way to block SSRF and command injection in CI/CD pipelines?

Yes, you can integrate validation into CI/CD workflows by checking the returnable exit codes and JSON outputs generated from scanning untrusted inputs, allowing your pipeline to strictly gate automated safe install workflows.

How do I sanitize emails and calendar items to stop path traversal attacks?

Sanitizing emails and calendar items to stop path traversal involves real-time filtering that marks suspicious external content, applying file and path checks to detect and block malicious traversal patterns before execution.

Do I need bash and jq to run command injection detection on untrusted inputs?

Yes, running command injection detection requires bash, grep, sed, jq, and npx dependencies, utilizing these tools to perform pattern-based detection and URL validation on untrusted inputs within your environment.

When should I not use pattern-based detection for credential exfiltration?

Pattern-based detection for credential exfiltration may be limited against novel or obfuscated zero-day payloads that do not match known signatures, meaning it should supplement but not replace strict URL allowlisting in highly sensitive environments.