secrets-manager

Detect, prevent, and remediate leaked credentials across codebases.

3|2|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JayRHa/AgentSkills --skill secrets-manager-jayrha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-manager
Source: https://github.com/JayRHa/AgentSkills/tree/main/secrets-manager
Command: npx skills add https://github.com/JayRHa/AgentSkills --skill secrets-manager-jayrha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Leaked credentials and mismanaged secrets present an active security risk; this skill helps you detect, prevent, and remediate secrets across codebases, configs, and CI/CD pipelines, while teaching best practices for safe secret handling.

Core Features & Use Cases

  • Secret scanning and classification: identifies hardcoded keys, tokens, and credentials and suggests corrective actions.
  • Pre-commit protection: enforces secret checks before commits with a reusable hook.
  • Remediation runbooks: guides revocation, history scrub, and rotation using references like leak-remediation.md and rotation-runbook.md.
  • ** vault/KMS integration and best practices**: outlines how to store and rotate credentials securely with dynamic secrets and workload identities.

Quick Start

Install secrets-manager in your project and run the built-in scanner to detect leaks, then apply the runbooks to remediate and rotate credentials.

Frequently Asked Questions about secrets-manager

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

FAQPage Schema
How do I detect and remediate leaked credentials in my codebase?

To detect and remediate leaked credentials, you can run a secret scanner to identify hardcoded API keys and tokens, then apply runbooks to revoke, scrub history, and rotate the exposed secrets. This workflow ensures complete remediation.

What is the best way to prevent hardcoded secrets from entering my git history?

Preventing hardcoded secrets from entering git history requires a pre-commit hook that enforces secret checks before commits are accepted. This stops leaked credentials like passwords and tokens from being committed into the repository.

How do I rotate exposed API keys and tokens after a leak?

Rotating exposed API keys and tokens after a leak involves following a remediation runbook that guides you through revoking the compromised credentials and generating new ones via vault or KMS integration.

Can I use this approach to secure .env file exposure in CI/CD pipelines?

Yes, you can secure .env file exposure in CI/CD pipelines by classifying the leaked secrets and applying secure storage workflows that inject credentials dynamically using workload identities rather than static files.

Does this workflow integrate with vault and KMS for dynamic secrets?

Yes, the workflow integrates with vault and KMS to securely store and rotate credentials using dynamic secrets and workload identities, ensuring that remediated credentials are managed safely after detection.