secrets

Detect exposed secrets and rotate credentials into secret managers.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill secrets-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/secrets
Command: npx skills add https://github.com/arbazkhan971/godmode --skill secrets-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams discover, remediate, and harden exposed secrets across codebases, git history, CI/CD pipelines, and deployment environments to prevent credential compromise and unauthorized access.

Core Features & Use Cases

  • Leak Detection: Scan the working tree and full git history for hardcoded credentials and sensitive environment files.
  • Remediation & Rotation: Revoke and rotate compromised credentials, migrate secrets into a secrets manager or Vault, and verify rollovers.
  • Prevention & Auditing: Install pre-commit secret scanning, enforce .env handling best practices, scrub git history when necessary, and generate access and exposure audit reports.
  • Use Case: During a security audit, automatically find a leaked API key, revoke it, rotate to a new secret stored in AWS Secrets Manager or Vault, update the application to use the new secret, and record the incident in a secrets audit log.

Quick Start

Scan the repository and git history for exposed credentials, revoke and rotate any verified leaks into a secret manager, install a gitleaks pre-commit hook if missing, and produce a secrets audit report.

Frequently Asked Questions about secrets

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

FAQPage Schema
How do I scan git history for leaked secrets and exposed credentials?

Scanning git history for leaked secrets involves checking the working tree and full commit history for hardcoded credentials and sensitive environment files. This detects exposed API keys and sensitive data to prevent unauthorized access.

What is the best way to revoke and rotate compromised credentials into a vault?

The best way to rotate compromised credentials is to revoke them, generate new secrets, and migrate them into a secrets manager or Vault. This verifies rollovers and minimizes service disruption during remediation.

How do I install a gitleaks pre-commit hook to prevent secret leaks?

Installing a gitleaks pre-commit hook prevents secret leaks by enforcing .env handling best practices and blocking hardcoded credentials before they enter the repository. This hardens prevention and automates auditing.

Does this approach support scrubbing git history for exposed environment files?

Yes, scrubbing git history for exposed environment files is supported to remediate leaked secrets. This process removes sensitive data from past commits while generating access and exposure audit reports for compliance.

Can I automate access auditing and onboarding for cloud secret stores?

You can automate access auditing and onboarding for cloud or on-prem secret stores. This applies to CI/CD pipelines and deployment environments, performing rotation and recording incidents in a secrets audit log.

How do I generate a secrets audit report after remediating exposed credentials?

To generate a secrets audit report after remediating exposed credentials, record the incident and access logs during the revocation and rotation process. This verifies the remediation steps and documents exposure for compliance.