secrets-scanner

Name: secrets-scanner
Availability: InStock
Author: jtucker9

Detect hardcoded secrets in codebases and Git history.

Updated Mar 13, 2026

Search Tags:#security #codebase #secrets #pre-commit #scanning #git-history #rotation

Ready to run

npx skills add https://github.com/jtucker9/mystuff --skill secrets-scanner-jtucker9

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secrets-scanner
Source: https://github.com/jtucker9/mystuff/tree/main/skills/security/secrets-scanner
Command: npx skills add https://github.com/jtucker9/mystuff --skill secrets-scanner-jtucker9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hardcoded secrets in code and commit history expose credentials and create security risks; this Skill detects exposed keys, tokens, and sensitive data to prevent breaches.

Core Features & Use Cases

Automated secret-detection patterns across repositories and git history
Pre-commit and CI integration to prevent leaks
Rotation guidance and remediation workflows for exposed credentials
Comprehensive audit of committed secrets with cleanup recommendations

Quick Start

Run the Secrets Scanner on your project to detect hardcoded secrets across current files and history and generate a remediation plan.

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 hardcoded secrets and exposed credentials?▼

Scanning git history for hardcoded secrets involves analyzing past commits to detect exposed credentials like API keys and tokens. This skill automates detection patterns across repositories to identify sensitive data and generate a remediation plan.

How do I set up pre-commit scanning to prevent secrets from leaking into my codebase?▼

Pre-commit scanning blocks hardcoded secrets before they enter a codebase by evaluating staged files. This skill integrates with pre-commit hooks to automatically detect exposed credentials and prevent sensitive data leaks during development.

What is the process for remediating and rotating committed secrets in git history?▼

Remediating and rotating committed secrets requires purging sensitive data from git history and invalidating the exposed credentials. This skill guides you through rotation procedures and cleanup workflows to secure repositories after a leak.

Can I use automated secret detection patterns across repositories of different programming languages?▼

Automated secret detection patterns apply to code repositories across various programming languages. This skill scans current worktrees and git histories regardless of language to identify hardcoded keys, tokens, and sensitive data.

How do I integrate secret scanning into my CI pipeline to audit exposed credentials?▼

Integrating secret scanning into CI pipelines audits exposed credentials by evaluating codebase changes during automated builds. This skill supports CI scanning to identify hardcoded secrets and generate cleanup recommendations for committed sensitive data.