security-secrets

Name: security-secrets
Availability: InStock
Author: justinlevinedotme

Detect AWS keys, API tokens, and private keys in codebases via regex scans.

7|2|Updated Jan 18, 2026

Search Tags:#audit #code-security #credential-detection #secret-redaction #secrets-scanning #regex-patterns #git-repositories

Ready to run

npx skills add https://github.com/justinlevinedotme/jalco-opencode --skill security-secrets

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-secrets
Source: https://github.com/justinlevinedotme/jalco-opencode/tree/main/opencode/.config/opencode/skills/security-secrets
Command: npx skills add https://github.com/justinlevinedotme/jalco-opencode --skill security-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rg, gitleaks, semgrep, trufflehog, and includes scripts (resource) components.

What problem does it solve?

Detect sensitive credentials and secret tokens in codebases.

Core Features & Use Cases

High-signal regex patterns for identifying secrets in codebases.
Redaction guidelines and safe reporting to prevent leakage.
Use Case: Run during security audits and CI checks to catch AWS keys, API tokens, and private keys.

Quick Start

Run the scanner on your repository to detect exposed credentials.

Frequently Asked Questions about security-secrets

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

FAQPage Schema

How do I scan a git repository for exposed API tokens and private keys?▼

Scanning a git repository for exposed API tokens and private keys involves running automated secret scanners with high-signal regex patterns to detect sensitive credentials. This process catches AWS keys and private keys during code reviews to prevent leaks.

What is the best way to detect AWS keys and credentials during a security audit?▼

Detecting AWS keys and credentials during a security audit is best achieved by running automated scans combined with high-signal regex patterns. This approach identifies secret tokens in codebases while providing redaction guidelines for safe reporting.

Do I need gitleaks and semgrep installed to scan codebases for secrets?▼

Installing tools like gitleaks, semgrep, trufflehog, and rg is required to scan codebases for secrets. These dependencies enable automated scans and high-signal regex pattern matching to catch sensitive credentials in your repositories.

How does secret redaction work when reporting security findings?▼

Secret redaction when reporting security findings works by applying redaction guidelines that mask sensitive credentials and secret tokens in scan results. This prevents accidental leakage of exposed AWS keys or API tokens during the sharing of audit reports.

Can I use automated secret scanning for CI checks and code reviews?▼

Automated secret scanning can be used for CI checks and code reviews to detect sensitive credentials in codebases. Running high-signal regex patterns during these processes catches AWS keys, API tokens, and private keys before they leak.