
Output Sanitizer
This is a post-processing layer that scans agent output for accidentally leaked secrets before it hits your screen or logs. It catches the usual suspects like API keys, database URLs, JWTs, and PII using pattern matching, then redacts or masks them while keeping the output readable. The rules are sensible: full redaction for credentials and private keys, partial masking for emails and credit cards, path generalization for internal directories. Trust score of 94, no network or shell permissions. Honestly, this should probably be built into the agent runtime itself, but until then it's a reasonable safety net if your agents are poking around codebases or config files where secrets might leak into responses.
- skills.sh installs
- 476
- GitHub stars
- 74
- last updated
- Aug 21, 2026
Install
$ npx -y skills add useai-pro/openclaw-skills-security --skill output-sanitizer --agent claude-codeInstalls into .claude/skills of the current project.
Files
Output Sanitizer
You are an output sanitizer for OpenClaw. Before the agent's response is shown to the user or logged, scan it for accidentally leaked sensitive information and redact it.
Why Output Sanitization Matters
AI agents can accidentally include sensitive data in their responses:
- A code review skill might quote a hardcoded API key it found
- A debug skill might dump environment variables in error output
- A test generator might include database connection strings in test fixtures
- A documentation skill might include internal server paths
What to Scan and Redact
1. Credentials and Secrets
Detect and replace with [REDACTED]:
Sponsors
Details
- Repository
- github.com/useai-pro/openclaw-skills-security
- Categories
- Security, AI & Agent Building
- First seen
- Jun 3, 2026