detect-hardcoded-secrets

Detect hardcoded secrets and credentials across source code languages.

3|Updated May 29, 2026
One-click install
npx skills add https://github.com/anortham/miller --skill detect-hardcoded-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-hardcoded-secrets
Source: https://github.com/anortham/miller/tree/main/.claude/skills/detect-hardcoded-secrets
Command: npx skills add https://github.com/anortham/miller --skill detect-hardcoded-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits code for exposed credentials, API keys, and secrets to prevent leaks across languages.

Core Features & Use Cases

  • Pattern-based secret detection
  • Assignment and secret format verification
  • Cloud provider pattern scanning
  • Verification of findings with symbol references

Quick Start

Run a security scan to surface potential secrets in the repository.

Frequently Asked Questions about detect-hardcoded-secrets

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

FAQPage Schema
How do I detect hardcoded secrets and API keys in my codebase?

Detect hardcoded secrets by running a pattern-based scan across your source code. This Skill applies a phased detection pipeline—pattern searches, assignment verification, cloud-provider key checks, and result validation—to surface exposed credentials, API keys, passwords, and connection strings across multiple languages in a structured format.

Can I scan for credentials during code reviews and security audits?

Yes, this Skill is designed for security audits and code reviews. It detects hardcoded secrets, API keys, and credentials to prevent credential leakage. Run it as part of your review workflow to surface potential exposures before code reaches production.

What types of secrets does the detector find?

The detector identifies API keys, passwords, credentials, cloud-provider keys, assignment patterns, and connection strings. It uses pattern-based detection and verification with symbol references to confirm findings across all major programming languages.

How does this approach differ from manual secret searches?

Automated secret detection applies consistent pattern matching and multi-stage verification across your entire codebase at once. This is faster and more comprehensive than manual reviews, catches variations in secret formats, and reduces human error in credential leakage investigations.

What's the best way to act on detected secrets?

After detection, rotate compromised credentials immediately, remove hardcoded secrets from source history, move credentials to environment variables or secret management systems, and implement pre-commit hooks to prevent future exposures.