secrets-exposure-detection

Detect exposed credentials and secrets across codebases, logs, and environments.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/marquesfelip/agents-and-skills --skill secrets-exposure-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-exposure-detection
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/secrets-exposure-detection
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill secrets-exposure-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The issue of secret leakage across codebases, logs, and deployment environments is a major security risk. This Skill provides automated detection and guidance to identify exposed credentials and secrets before they are exploited.

Core Features & Use Cases

  • Detect secrets across Git history, source code, CI/CD pipelines, and runtime logs.
  • Integrate with common scanners (Gitleaks, TruffleHog, Semgrep Secrets) for pre-commit, PR, and scheduled scans.
  • Provide remediation guidance and rotation workflows to minimize blast radius and expedite incident response.

Quick Start

Configure and run the secret-detection workflow to scan your repository for exposed credentials using your preferred scanners and gate the results in CI.

Frequently Asked Questions about secrets-exposure-detection

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

FAQPage Schema
How do I detect exposed secrets and credentials in my Git history?

Secret exposure detection scans Git history and source code to identify exposed credentials before exploitation. It integrates scanners like Gitleaks, TruffleHog, and Semgrep Secrets to automate finding leaked tokens and keys across repositories.

Can I use Gitleaks and TruffleHog to set up pre-commit hooks and CI gates?

Yes, secret exposure detection supports integrating Gitleaks, TruffleHog, and Semgrep Secrets as pre-commit hooks and CI gates. This prevents credential leakage by scanning source code and blocking commits or pull requests that contain exposed secrets.

What is the best way to scrub exposed credentials from runtime logs?

Secret exposure detection includes log scrubbing workflows to find and remove exposed credentials from runtime logs. It leverages Semgrep Secrets and similar scanners to identify sensitive data in deployment environments and provides remediation guidance.

How do I handle incident response when a secret leakage occurs in CI/CD pipelines?

Secret exposure detection provides incident-response workflows for software teams to manage secret leakage in CI/CD pipelines. It offers remediation guidance and rotation workflows to minimize blast radius and expedite recovery from exposed credentials.

Does Semgrep Secrets work for scheduled scans across codebases and environments?

Semgrep Secrets is supported alongside Gitleaks and TruffleHog for scheduled scans across codebases and environments. Secret exposure detection enforces these scanners to continuously monitor for exposed credentials and prevent unauthorized access.