secrets_scan

Scan repositories, Kubernetes pods, and git configurations for leaked credentials.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/TheMacroeconomicDao/decentralized-social-platform --skill secrets-scan-themacroeconomicdao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets_scan
Source: https://github.com/TheMacroeconomicDao/decentralized-social-platform/tree/main/ORACLE/openclaw-k8s/workspace/skills/secrets-scan
Command: npx skills add https://github.com/TheMacroeconomicDao/decentralized-social-platform --skill secrets-scan-themacroeconomicdao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill proactively identifies and reports leaked credentials, tokens, and sensitive information embedded within your codebase, live environments, and git history, preventing potential security breaches.

Core Features & Use Cases

  • Repository Scanning: Detects hardcoded API keys, tokens, and sensitive patterns in files across specified directories.
  • Live Pod Inspection: Checks for secrets in .env files, git configurations, and other live environment artifacts.
  • Git History Analysis: Scans git remote URLs for embedded tokens and verifies credential helper configurations.
  • Use Case: Before merging a pull request, run this Skill to ensure no accidental exposure of API keys or tokens has occurred in the new code.

Quick Start

Run the secrets scan skill to check the repository for any leaked credentials.

Frequently Asked Questions about secrets_scan

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

FAQPage Schema
How do I scan for leaked credentials and tokens in my codebase before merging?▼

Scanning for leaked credentials before a merge involves checking specified directories for hardcoded API keys and sensitive patterns. This process automates repository scanning to identify exposed tokens and prevent accidental secret leakage in new code.

Can I check live Kubernetes pods for insecure configurations and .env files?▼

Yes, you can inspect live Kubernetes pods for insecure configurations. The process checks live environments for secrets within `.env` files, git configurations, and other artifacts to detect sensitive data exposure in deployed containers.

How does git history analysis find embedded tokens in remote URLs?▼

Git history analysis finds embedded tokens by scanning git remote URLs for hardcoded credentials. It verifies credential helper configurations and checks setups to ensure access tokens are not insecurely exposed in your repository configuration.

Do I need bash, kubectl, and git installed to run a secrets scan?▼

Yes, you need bash, kubectl, and git installed to run a secrets scan. The process requires these command-line tools to execute pattern searches, inspect live pod environments, and verify git configurations for sensitive data.

What is the best way to secure code from leaked secrets in repository files?▼

The best way to secure code from leaked secrets is to run automated pattern searches across your repository directories. This identifies hardcoded API keys, tokens, and insecure configurations before they cause potential security breaches.