security-secrets-and-logging

Enforce redaction and safe logging to prevent credential and PII leakage.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/JuanTaco4You/codex-agent-skills --skill security-secrets-and-logging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-secrets-and-logging
Source: https://github.com/JuanTaco4You/codex-agent-skills/tree/main/security-secrets-and-logging
Command: npx skills add https://github.com/JuanTaco4You/codex-agent-skills --skill security-secrets-and-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when handling sensitive data, credentials, tokens, or user PII to avoid leaks and unsafe logging.

Core Features & Use Cases

  • Redaction and safe-logging practices across codebases and deployments
  • Secret storage guidance and environment-aware handling
  • Input validation and access control to prevent leakage in logs

Quick Start

Use this skill to implement redaction utilities and secure logging in your project.

Frequently Asked Questions about security-secrets-and-logging

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

FAQPage Schema
How do I prevent secrets and PII from leaking into application logs?

Redaction utilities and safe logging practices prevent secrets and PII from leaking into application logs by sanitizing credentials, tokens, and user data before output generation. This skill provides guidance to enforce these protective measures across your codebase.

What is the best way to manage secret storage across different environments?

Environment-aware handling and access control provide the best way to manage secret storage across different environments. This skill offers secret management guidance to ensure credentials are validated and secured within codebases and CI/CD pipelines.

How do I implement redaction for sensitive data in my CI/CD pipelines?

To implement redaction for sensitive data in CI/CD pipelines, enforce safe logging and input validation throughout the deployment process. This skill applies protective rules to prevent leakage of tokens and PII in runtime environments and pipeline outputs.

Can I use this approach to check repository hygiene for hidden credentials?

You can use this approach to check repository hygiene by applying recommendations for input validation and secret management. It helps identify and redact hidden credentials, ensuring sensitive data is not exposed in logs or stored improperly in codebases.

Does this safe logging guidance work for both codebases and runtime environments?

This safe logging guidance works for both codebases and runtime environments. It enforces redaction utilities and secure handling of PII across applications, CI/CD pipelines, and live deployments to prevent credential leakage.