secret-handling

To prevent AI agents from reading environment secrets, you enforce strict prohibitions on .env file access. This skill blocks agents from reading .env files and guides them to use safe placeholders like .env.example instead.

To stop secrets from being committed to code repository history, you enforce pre-commit validation. This skill blocks commits containing credentials and prevents secrets from appearing in committed files.

The best way to redact sensitive content in automated agent workflows is to replace secrets with placeholders. This skill prevents secret exposure in logs and history by enforcing safe alternatives and redaction.

Yes, you can use .env.example files for schema and testing without exposing credentials. This skill explicitly allows reading .env.example, .env.sample, or .env.template while blocking actual .env files.

To enforce safe credential handling policies in automated code repositories, you apply strict rules on agent file access. This skill codifies prohibitions on secret file reads and enforces pre-commit validation to block credential exposure.