security-guardrails

Redact sensitive tokens from agent responses, logs, and tool outputs.

2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/hiyenwong/ai_collection --skill security-guardrails-hiyenwong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-guardrails
Source: https://github.com/hiyenwong/ai_collection/tree/main/collection/skills/security-guardrails
Command: npx skills add https://github.com/hiyenwong/ai_collection --skill security-guardrails-hiyenwong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The guardrails enforce security by preventing secrets, credentials, and other sensitive data from appearing in outputs, logs, or tool interactions.

Core Features & Use Cases

  • Automatic detection and redaction of sensitive information in responses and generated content
  • Safe handling for configuration and logs to avoid exposing secrets
  • Clear guidance and enforcement for agents to refuse unsafe prompts and data exfiltration attempts

Quick Start

Enable and rely on the guardrails to automatically redact sensitive data from all agent responses and logs.

Frequently Asked Questions about security-guardrails

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

FAQPage Schema
How do I prevent secrets from leaking in agent outputs and logs?

To prevent secrets from leaking in agent outputs, you can use sanitize-and-redact logic that automatically detects sensitive tokens and replaces them with placeholders across responses, logs, and tool interactions.

What is output sanitization for AI agents and how does it work?

Output sanitization for AI agents is a process that filters generated content and tool interactions to identify sensitive data, enforcing mandatory redaction by replacing confidential values with safe placeholders before returning responses.

How do I redact sensitive tokens from file outputs and external tool calls?

You can redact sensitive tokens from file outputs and external tool calls by applying mandatory sanitize-and-redact logic that supports safe file reading and filters outputs to replace confidential values with placeholders.

Can I use these guardrails to block unsafe prompts and data exfiltration attempts?

Yes, these guardrails provide clear guidance and enforcement for agents to refuse unsafe prompts and data exfiltration attempts, ensuring sensitive configuration data and credentials remain private across all workflows.

Does output redaction work across all agent environments and workflows?

Yes, output redaction is applicable to all agent environments and workflows where confidential data must remain private, including prompts, file outputs, and external tool calls.

Why are credentials still appearing in my agent logs and generated content?

Credentials appear in agent logs because mandatory output filtering is not enabled; applying sanitize-and-redact logic automatically detects and replaces sensitive information with placeholders to prevent exposure.