AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

env-secrets-manager

Use when auditing .env files, planning credential rotation, chasing a missing env var in production or hardening a repo against leaked secrets. Scans for committed secrets and drift with env_auditor.py.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--env-secrets-manager at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 3

references/secret-patterns.md

Secret Pattern Reference

Detection Categories

Critical

  • OpenAI-like keys (sk-...)
  • GitHub personal access tokens (ghp_...)
  • AWS access key IDs (AKIA...)

High

  • Slack tokens (xox...)
  • Private key PEM blocks
  • Hardcoded assignments to secret, token, password, api_key

Medium

  • JWT-like tokens in plaintext
  • Suspected credentials in docs/scripts that should be redacted

Severity Guidance

  • critical: immediate rotation required; treat as active incident
  • high: likely sensitive; investigate and rotate if real credential
  • medium: possible exposure; verify context and sanitize where needed

Response Playbook

  1. Revoke or rotate exposed credential.
  2. Identify blast radius (services, environments, users).
  3. Remove from code/history where possible.
  4. Add preventive controls (pre-commit hooks, CI secret scans).
  5. Verify monitoring and access logs for abuse.

Preventive Baseline

  • Commit only .env.example, never .env.
  • Keep .gitignore patterns for env and key material.
  • Use secret managers for staging/prod.
  • Redact sensitive values from logs and debug output.