secrets-scanner

Detect leaked credentials in code repositories with Gitleaks, detect-secrets, and TruffleHog.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Camilo8902/GabyCosmetics --skill secrets-scanner-camilo8902
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-scanner
Source: https://github.com/Camilo8902/GabyCosmetics/tree/main/.claude/skills/secrets-scanner
Command: npx skills add https://github.com/Camilo8902/GabyCosmetics --skill secrets-scanner-camilo8902

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @aws-sdk/client-secrets-manager, zod, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill prevents sensitive information like API keys, tokens, and passwords from being accidentally exposed in your codebase, safeguarding against security breaches.

Core Features & Use Cases

  • Automated Secret Detection: Scans code for common patterns of leaked credentials.
  • Pre-commit Hooks: Integrates with Git to catch secrets before they are committed.
  • CI Integration: Adds automated secret scanning to your continuous integration pipeline.
  • Remediation Guidance: Provides steps to revoke and remove compromised secrets.
  • Use Case: Ensure no API keys or database passwords are ever committed to your public GitHub repository.

Quick Start

Run the secrets-scanner skill to scan the current directory for any leaked credentials.

Frequently Asked Questions about secrets-scanner

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

FAQPage Schema
How do I scan my code repository for leaked API keys and passwords?

You can prevent accidental credential exposure by scanning your repository for leaked API keys and passwords. This skill detects sensitive information using Gitleaks, detect-secrets, and TruffleHog to safeguard against security breaches in your codebase.

How do I set up pre-commit hooks to catch secrets before they are committed?

You can prevent accidental credential exposure by scanning your repository for leaked API keys and passwords. This skill detects sensitive information using Gitleaks, detect-secrets, and TruffleHog to safeguard against security breaches in your codebase.

Can I add automated secret scanning to my continuous integration pipeline?

Yes, you can integrate automated secret scanning into your continuous integration pipeline. This skill supports CI checks to detect and prevent leaked credentials, API keys, and tokens within code repositories during the build process.

What should I do if the scanner finds compromised secrets in my Git history?

If the scanner finds compromised secrets, you should follow the provided remediation guidance to revoke and remove them. This skill provides specific steps to securely handle detected credentials, API keys, and tokens to mitigate security risks.

Does this secret detection tool support custom scanning rules?

Yes, this secret detection tool supports custom scanning rules. You can define specific patterns for credentials, API keys, and tokens alongside the default detection mechanisms provided by Gitleaks, detect-secrets, and TruffleHog.