skills.rest
anishi1222
anishi1222COMMUNITY
Explore all skills by this author →
WebsiteGitHub

secret-scan

Detect hardcoded API keys, tokens, passwords, and secret keys in code repositories.

Updated Feb 20, 2026
Search Tags:#security audit#secret detection#credential management#code scanning#password protection
One-click install
npx skills add https://github.com/anishi1222/multi-agent-code-reviewer --skill secret-scan-anishi1222
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secret-scan
Source: https://github.com/anishi1222/multi-agent-code-reviewer/tree/main/.github/skills/secret-scan
Command: npx skills add https://github.com/anishi1222/multi-agent-code-reviewer --skill secret-scan-anishi1222

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identifies hardcoded sensitive information within code repositories, preventing accidental exposure of keys, tokens, passwords, and other credentials.

Core Features & Use Cases

  • Hardcoded Secret Detection: Scans for API keys, tokens, passwords, secret keys, and cloud credentials within codebase files.
  • Security Compliance: Assists in maintaining compliance with security standards by highlighting potential security vulnerabilities.
  • Use Case: When conducting code reviews or audits, the Skill can quickly alert developers to remove sensitive information that might be mistakenly hardcoded in the codebase.

Quick Start

Analyze the code for potential hardcoded secrets with the command: secret-scan run --repo owner/repo.

Frequently Asked Questions about secret-scan

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

FAQPage Schema
How do I scan my codebase for hardcoded API keys and passwords?▼

Scanning a codebase for hardcoded API keys and passwords involves analyzing repository files to detect embedded sensitive credentials. This process highlights potential security vulnerabilities by locating tokens and keys mistakenly committed to the codebase.

What types of hardcoded secrets can be detected in a code repository?▼

Hardcoded secret detection scans for API keys, tokens, passwords, secret keys, and cloud credentials within codebase files. Identifying these sensitive credentials helps maintain security compliance and prevents accidental data exposure.

Can I use automated secret detection for security compliance audits during code reviews?▼

Automated secret detection can be used for security compliance audits during code reviews. It quickly alerts developers to remove sensitive information, such as passwords and tokens, mistakenly hardcoded in the codebase to prevent data breaches.

Does hardcoded credential scanning work with any code repository?▼

Hardcoded credential scanning is applicable to any project needing to prevent data breaches due to misconfiguration of sensitive credentials. It audits code repositories by analyzing file contents for embedded API keys and tokens.

What is the best way to prevent accidental exposure of cloud credentials in source code?▼

The best way to prevent accidental exposure of cloud credentials in source code is conducting automated security audits. Scanning repositories identifies hardcoded keys, tokens, and passwords to highlight potential vulnerabilities before they cause data breaches.

Related Skills

Explore More Software Engineering Skills→
ofelixdevofelixdev

vulnerability-scanner

Scan project dependencies, hardcoded secrets, code patterns, and configurations for security vulnerabilities.

Community
Advanced
jamesjlundinjamesjlundin
32

secrets-scanner

Scan codebases for secrets, credentials, and PII patterns.

Community
Intermediate
TeiNamTeiNam
12

laravel-verification

Automate Laravel project verification for CI/CD pipelines.

Community
Advanced
ChatAndBuildChatAndBuild
1

Query Token Audit

Evaluate token security across blockchain platforms using audit APIs.

Official
Intermediate