seed-secret-scrubber

Detect committed secrets in code repositories and report file:line references with redaction patches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JBODE-mhhs/Zeus2.0-public --skill seed-secret-scrubber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seed-secret-scrubber
Source: https://github.com/JBODE-mhhs/Zeus2.0-public/tree/main/community/seeds/seed-secret-scrubber
Command: npx skills add https://github.com/JBODE-mhhs/Zeus2.0-public --skill seed-secret-scrubber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan a file or directory for accidentally-committed secrets — API keys, JWTs, AWS access keys, private keys, .env values. High-precision regex set; reports findings with file:line and a redaction patch.

Core Features & Use Cases

  • Regex-based detection to identify common secret patterns across codebases.
  • Disposition guidance to rotate secrets, replace with fake data, or scrub history; supports pre-commit hooks and CI workflows.
  • Actionable remediation reports with file:line references and redaction patches for secure commits.

Quick Start

Run seed-secret-scrubber on your project to detect secrets and generate redacted patches before committing.

Frequently Asked Questions about seed-secret-scrubber

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

FAQPage Schema
How do I scan my codebase for accidentally committed API keys and secrets?

Scan your codebase for committed secrets by applying a high-precision regex set across project files. This identifies sensitive values like API keys and tokens, reporting findings with file:line references and a redaction patch.

Can I detect leaked credentials in a pre-commit hook before pushing code?

Yes, you can detect leaked credentials in a pre-commit hook. Running the scan before commits catches sensitive values early, generating actionable remediation reports to ensure secure commits.

What is the best way to redact sensitive environment variables from source files?

The best way to redact sensitive environment variables is using regex-based detection to identify common secret patterns. The scan reports findings with file:line references and provides a redaction patch to replace exposed values.

Does regex-based secret detection work for AWS access keys and JWTs?

Regex-based secret detection works for AWS access keys and JWTs by matching common secret patterns. The scan applies a high-precision regex set to identify these specific sensitive values across your codebase.

What should I do after finding exposed private keys in my repository?

After finding exposed private keys, follow disposition guidance to rotate secrets, replace them with fake data, or scrub history. The scan provides a redaction patch to help secure your committed files.