secret-detection

Detect hard-coded secrets in code repositories and generate remediation guidance.

83|8|Updated May 6, 2026
One-click install
npx skills add https://github.com/Q16G/aster --skill secret-detection-q16g
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-detection
Source: https://github.com/Q16G/aster/tree/main/skills/code-audit/secret-detection
Command: npx skills add https://github.com/Q16G/aster --skill secret-detection-q16g

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects hard-coded secrets in codebases to prevent credential leakage and reduce security risk.

Core Features & Use Cases

  • Secret scanning in repositories for API keys, tokens, and credentials.
  • Generates actionable remediation guidance and risk scoring for found secrets.
  • Use Case: Integrate into CI pipelines to fail builds when secrets are detected and alert developers.

Quick Start

Scan a target repository to identify hard-coded secrets and generate a remediation plan.

Frequently Asked Questions about secret-detection

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

FAQPage Schema
How do I detect hard-coded secrets and API keys in my codebase?

To detect hard-coded secrets in a codebase, you can scan your source files to identify embedded API keys, tokens, and credentials. The process applies static analysis rules to prevent credential leakage and generates actionable remediation guidance.

Can I integrate secret detection into my CI/CD pipeline to fail builds?

Yes, you can integrate secret detection into CI/CD pipelines to fail builds when hard-coded secrets are discovered. This alerts developers during code reviews and prevents credentials from reaching production repositories.

What is static analysis for code security and how does it handle found credentials?

Static analysis for code security scans repositories to detect hard-coded credentials without executing the code. It logs findings locally, provides risk scoring for the discovered secrets, and offers remediation guidance without exfiltrating your data.

Does secret scanning exfiltrate my source code or found credentials?

No, secret scanning does not exfiltrate your source code or found credentials. The detection process satisfies rules locally, logs findings on your machine, and provides remediation guidance without sending your data externally.

What is the best way to generate remediation guidance for leaked tokens in code reviews?

The best way to generate remediation guidance for leaked tokens is to run a repository scan that identifies the credentials and automatically produces actionable risk scoring and remediation steps tailored to the found secrets.