Results for “secrets”

Store, retrieve, and manage secrets like passwords, API keys, and connection strings using Azure Key Vault with the Java SDK.

Integrate gitleaks and trufflehog into CI/CD pipelines to detect leaked secrets before deployment.

Manage production secret infrastructure with HashiCorp Vault, cloud secret stores, automated rotation, and audit logging.

Manage cryptographic keys and secrets in Azure Key Vault using the @azure/keyvault-keys and @azure/keyvault-secrets SDKs for TypeScript.

Manage secrets and keys in Azure Key Vault using the JavaScript SDK, including CRUD operations, cryptographic functions, backup/restore, and key rotation.

Secure Quarkus applications with authentication, authorization, input validation, and secrets management.

Configures HashiCorp Vault dynamic secrets engines for database credentials, AWS IAM keys, and PKI certificates with automatic generation, lease management, and credential rotation.

Secure Quarkus applications with authentication, authorization, input validation, and secrets management best practices.

Manages environment variables securely by masking sensitive values, validating schemas, and injecting secrets into commands without exposing them.

Manage environment variables and secrets in Claude Code sessions without exposing their values to logs, diffs, or context.

Manage secrets, cryptographic keys, and certificates in Azure Key Vault using the Python SDK.

Scan source code repositories, CI/CD pipelines, and configuration files for exposed AWS credentials using TruffleHog, git-secrets, and AWS-native detection mechanisms to prevent credential theft and unauthorized account access.

Manage environment variables and secrets securely in Claude Code sessions, ensuring sensitive values are never exposed in logs, diffs, or context.

Manages environment variables and secrets in Claude Code sessions without exposing values, using Varlock for validation, masking, and secure command execution.

Audit MCP server configurations for security issues including secrets exposure, shell injection, unpinned dependencies, and unapproved servers.

Configure and manage GitHub secret scanning, push protection, custom patterns, and alert remediation.

Local-first secret scanning for repos and git history. Use before every push, when scanning for exposed keys, checking for committed credentials, or auditing a repo for accidental secret leaks. Designed for Nick's workflow and safer than forcing suspicious marketplace secret scanners.

Provides a comprehensive security checklist and code patterns for authentication, input validation, secrets management, SQL injection prevention, XSS, CSRF, rate limiting, and sensitive data exposure.

Manages environment variables securely by validating against a schema, masking sensitive values, and injecting validated secrets into commands without exposing them.

Audit the working tree and git history for exposed credentials and mis-scoped keys, then a rotate-vs-relocate plan. Use when "hardcoded secrets", "did I commit a key", "secret scan", "is my .env safe", or "rotate keys". Do not fire for "RLS audit" or generic "security burndown".

Use this skill for secret inventory, env vars, rotation plans, safe dev/prod separation, leak response. Trigger when the task involves security work related to Secrets Env Rotation, implementation, audits, debugging, strategy, or validation.

Scans agent skills for security issues including prompt injection, malicious scripts, excessive permissions, secret exposure, and supply chain risks.

Detect and prevent hardcoded secrets in git repositories using Gitleaks, including pre-commit hooks, CI/CD integration, custom rules, baseline management, and remediation workflows.

Use this when reviewing or designing how secrets, API keys, service credentials, signing keys, tokens, and environment-specific credentials are stored, loaded, rotated, and kept out of untrusted runtimes.

Implements security-sensitive changes with conservative trust boundaries, secret protection, tests, and verification.

Documents AI-built apps with architecture, permissions, secrets, and test coverage maps to make them reviewable before shipping.

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

Provides a security checklist and code patterns for authentication, input validation, secrets management, SQL injection prevention, XSS, CSRF, rate limiting, and sensitive data handling.

Bagman