Skip to main content
prompt GP ChatGPT

Secrets Management taste — ChatGPT prompt: what it does

Secrets Management taste — a prompt for ChatGPT that defines security standards and best practices for secrets management.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Secrets Management taste does

The prompt sets security standards for handling secrets, API keys, and credentials across codebases and deployment pipelines. It guides the model to enforce practices such as keeping real .env files out of git, storing production credentials in Vault, AWS Secrets Manager, GCP Secret Manager, or 1Password, and running secret scanners like gitleaks in CI.

The rules prohibit committing secrets to git history, require rotating any credential that touched a repository, and mandate scoped permissions for every service. Guidelines cover OIDC federation, runtime secret injection via mounted files, log redaction, and automated rotation without downtime.

Applications are expected to validate required secrets on startup and fail fast when keys are missing. The prompt also outlines audit logging, SSO access for humans, and encryption for git-native configs using SOPS or Sealed Secrets.

What it helps with

  • prevent committing secrets to git and test branches
  • set up secret scanning in CI and pre-commit hooks
  • store production credentials in dedicated managers
  • enforce automated rotation and secure credential injection
  • validate required secrets on application startup

Example prompts for the agent

  • Apply secrets management taste rules to this repository
  • Review our configuration for hardcoded secrets following secrets management taste
  • Help set up secure secret rotation according to secrets management taste

How to install Secrets Management taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Secrets Management taste

How to install Secrets Management taste in Claude Code?

To install, place the prompt file at .claude/commands/prompts.csv.md in your project root.

What does Secrets Management taste do?

It provides a comprehensive set of security rules and engineering practices for managing secrets, keys, rotation, and access control.

What tools and services are referenced in the prompt?

The prompt references gitleaks, trufflehog, Vault, AWS Secrets Manager, GCP Secret Manager, 1Password, OIDC, SOPS, and Sealed Secrets.

Source text

prompts.csv · CC0-1.0
# Secrets Management taste of a security-minded platform engineer
- Never commit secrets to git, including in tests, examples or old branches; treat any secret that touched a repo as compromised and rotate it. Confidence: 1.00
- Run secret scanning (gitleaks, trufflehog or the platform's built-in scanner) as a pre-commit hook and in CI on every push. Confidence: 0.90
- Keep a committed `.env.example` with names and dummy values, and gitignore every real `.env` file. Confidence: 0.90
- Store production secrets in a dedicated manager such as Vault, AWS Secrets Manager, GCP Secret Manager or 1Password, never in wikis or chat. Confidence: 0.95
- Prefer short-lived, workload-issued credentials (OIDC federation, IAM roles, Vault dynamic secrets) over long-lived static keys. Confidence: 0.90
- Use OIDC from CI to cloud providers instead of storing cloud access keys as CI secrets. Confidence: 0.90
- Scope every credential to one service, one environment and the least privilege it needs. Confidence: 0.95
- Never share secrets between staging and production, so a leak in one cannot unlock the other. Confidence: 0.95
- Inject secrets at runtime through the platform (mounted files or environment variables) rather than baking them into images or build artifacts. Confidence: 0.90
- Prefer mounted secret files over environment variables for highly sensitive values, since env vars leak into crash dumps, child processes and debug pages. Confidence: 0.70
- Automate rotation on a schedule and design apps to reload credentials without a redeploy. Confidence: 0.80
- Support two valid versions of a secret during rotation so it can happen without downtime. Confidence: 0.80
- Redact secrets in logs, traces and error reports with explicit filters, and test that the redaction works. Confidence: 0.90
- Use envelope encryption with a KMS for application-level encryption keys and keep the key-encryption key out of the app. Confidence: 0.80
- Encrypt secrets that must live in git (for example GitOps manifests) with SOPS or Sealed Secrets, never as plain Kubernetes Secrets. Confidence: 0.85
- Audit-log every secret read and alert on unusual access patterns. Confidence: 0.75
- Maintain a written revoke-and-rotate runbook for each critical credential so a leak response takes minutes, not days. Confidence: 0.85
- Give humans access through SSO and time-limited elevation instead of shared admin passwords. Confidence: 0.90
- Validate required secrets at startup and fail fast with a clear message that names the missing key but never prints its value. Confidence: 0.85
- Do not roll your own encryption or token formats; use well-reviewed libraries and the provider's primitives. Confidence: 0.95

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Security →

From the same set218

The whole set →
Dependency Management taste Dependency Management taste — a prompt for ChatGPT and Claude.ai that configures AI around a strict dependency management philosophy. Prevents surprise breakages. GP ChatGPT ★ 178,201repo stars Internationalization taste The Internationalization taste ChatGPT prompt sets out product internationalization practices. It covers localized UI text, data formats, and public pages. GP ChatGPT ★ 178,201repo stars API Rate Limiting taste API Rate Limiting taste — a prompt for ChatGPT that defines rate limiting rules for API endpoints. Helps design backend protection against abuse and traffic spikes. GP ChatGPT ★ 178,201repo stars Python Type Hints taste The Python Type Hints taste ChatGPT prompt sets conventions for typing Python code. It covers annotations, type choices, and static checking. GP ChatGPT ★ 178,201repo stars Tokio Async Rust taste The Tokio Async Rust taste prompt for ChatGPT sets engineering conventions for asynchronous Rust services built with Tokio. It applies while writing or reviewing code that handles task cancellation, network timeouts, and shutdown. GP ChatGPT ★ 178,201repo stars Tailwind CSS taste Tailwind CSS taste is a prompt for ChatGPT, Claude.ai, and Claude Code that sets utility-first styling rules, design tokens, and bans arbitrary pixel sizes in Tailwind CSS code. GP ChatGPT ★ 178,201repo stars Vite Frontend Tooling taste The Vite Frontend Tooling taste ChatGPT prompt sets preferences for building frontend projects with Vite. It covers app setup, type checks, tests, and release builds. GP ChatGPT ★ 178,201repo stars Linux Server Hardening taste Linux Server Hardening taste — a prompt for ChatGPT provides an operations engineering ruleset for hardening Linux servers. It guides base image setup, SSH access policies, and automated configuration via Ansible or cloud-init. GP ChatGPT ★ 178,201repo stars

Project sponsors

Companies that keep this analytics open