secrets-scanner

Detect committed credentials in codebases and git history.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/FrogAi/Xenopus --skill secrets-scanner-frogai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-scanner
Source: https://github.com/FrogAi/Xenopus/tree/main/Gemini/Skills/Gemini%203.1%20Pro/secrets-scanner
Command: npx skills add https://github.com/FrogAi/Xenopus --skill secrets-scanner-frogai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects committed credentials and secrets in codebases and git history to prevent exposure and compromise.

Core Features & Use Cases

  • Live pattern catalogs from major detectors (GitHub Advanced Security, truffleHog, gitleaks, detect-secrets, Semgrep)
  • Multi-detector fusion: correlate pattern hits with entropy and context for high-confidence findings
  • History + working-tree analysis: detects secrets in current code and across commit history
  • Remediation workflow: rotation guidance, history cleanup, and blast-radius audit; pre-commit-hook and CI workflow snippets
  • Standardized output: JSON/markdown reports with redacted values and handoffs to rotation coordinators

Quick Start

Scan a repository to detect secrets in current code and history and produce redacted findings with remediation guidance.

Frequently Asked Questions about secrets-scanner

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

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

To scan git history for secrets, analyze working-tree files and full commit history using multi-detector fusion. This correlates live pattern matches with entropy and context to produce high-confidence findings and standardized JSON or markdown reports.

How do I detect secrets in code during CI environment workflows?

Detect secrets in CI environments by integrating live pattern fetching and contextual enrichment into pipeline workflows. This scans repository code against major detector catalogs to prevent credential exposure before deployment.

What is the best way to remediate exposed credentials found in a codebase?

The best way to remediate exposed credentials is to use rotation guidance, history cleanup, and blast-radius audits. This approach generates redacted reports and provides handoffs to rotation coordinators for secure recovery.

Does multi-detector fusion reduce false positives when scanning for secrets?

Multi-detector fusion reduces false positives by correlating pattern hits from major detectors with entropy and context. This contextual enrichment ensures high-confidence findings when scanning real-world repositories for committed credentials.

Can I use live pattern catalogs from existing detectors like truffleHog and gitleaks?

You can use live pattern catalogs from GitHub Advanced Security, truffleHog, gitleaks, detect-secrets, and Semgrep. The scanner fetches these patterns in real-time to match against working-tree and historical codebase content.

How do I generate redacted reports for secrets found in my repository?

Generate redacted reports by running a scan that outputs standardized JSON or markdown formats. These reports mask exposed secret values and include remediation handoffs to guide credential rotation and history cleanup.