skills.rest
0xjitsu
0xjitsuCOMMUNITY
Explore all skills by this author →
Website𝕏@0xjitsuGitHub

secret-scanner

Scan full git history for leaked secrets and produce masked remediation reports.

1|Updated Apr 13, 2026
Search Tags:#git#security#audit#remediation#credentials#secret-detection#secret-scanner
One-click install
npx skills add https://github.com/0xjitsu/jitsu-skills --skill secret-scanner-0xjitsu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secret-scanner
Source: https://github.com/0xjitsu/jitsu-skills/tree/main/skills/secret-scanner
Command: npx skills add https://github.com/0xjitsu/jitsu-skills --skill secret-scanner-0xjitsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans a repository's full git history to find leaked secrets, API keys, tokens, and credentials so teams can identify exposures that are hidden in past commits, deleted files, or other branches.

Core Features & Use Cases

  • Full-history scanning: Analyze diffs across all commits and branches rather than only the working tree to locate secrets introduced and later removed.
  • Severity-ranked findings: Classify detections as CRITICAL, HIGH, or MEDIUM using provider-specific regex patterns and present results in a prioritized table.
  • Safe output and remediation: Always mask secrets in reports, provide explicit rotation and git-history remediation commands (e.g., git-filter-repo and force-push warnings), and require confirmation before any history rewrite.
  • Use Case: Run a pre-publish security audit to ensure no credentials will be exposed when open-sourcing a repository or during a compliance review.

Quick Start

Ask the assistant to scan the repository's full git history for exposed secrets and return a severity-ranked, masked findings table with remediation guidance.

Frequently Asked Questions about secret-scanner

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

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

Scan git history for leaked secrets by analyzing diffs across all commits and branches to locate exposed API keys, tokens, and credentials introduced and later removed. It inspects additions in diffs using regex-based secret patterns.

What is the best way to find exposed API keys in past commits?▼

Finding exposed API keys in past commits requires a full-history scan that analyzes diffs across all branches rather than only the working tree. Detections are classified as CRITICAL, HIGH, or MEDIUM using provider-specific regex patterns.

Can I use a secret scanner for pre-publish security audits and compliance reviews?▼

You can use a secret scanner for pre-publish security audits and compliance reviews to ensure no credentials will be exposed when open-sourcing a repository. It operates read-only locally to inspect history without performing network calls.

Does secret scanning automatically rewrite git history to remove tokens?▼

Secret scanning does not automatically rewrite git history to remove tokens. It operates read-only, produces explicit remediation commands like git-filter-repo with force-push warnings, and requires confirmation before any history rewrite.

How are detected credentials masked in secret detection reports?▼

Detected credentials are always masked in secret detection reports to ensure safe output. The findings are presented in a severity-ranked, masked table alongside explicit rotation and git-history remediation guidance.

Related Skills

Explore More Software Engineering Skills→
cryborg1211cryborg1211

vc:watzup

Summarize repository state and active plans for handoff.

Community
Intermediate
drvossdrvoss
42

secret-detection

Detect hardcoded API keys, tokens, and passwords in source code and git history.

Community
Intermediate
RoxabiRoxabi
9

ci-setup

Automate CI/CD pipeline setup with GitHub Actions, TruffleHog, and Dependabot.

Official
Advanced
arbazkhan971arbazkhan971
26

secrets

Detect exposed secrets and rotate credentials into secret managers.

Community
Advanced