env-secrets-scan

Scan source code, git history, and templates for secrets.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/mitchellvandusen-cell/Flask-Webhook --skill env-secrets-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-secrets-scan
Source: https://github.com/mitchellvandusen-cell/Flask-Webhook/tree/main/.claude/skills/env-secrets-scan
Command: npx skills add https://github.com/mitchellvandusen-cell/Flask-Webhook --skill env-secrets-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures the security of InsuranceGrokBot by identifying and reporting on potential secret leaks in code, git history, and templates.

Core Features & Use Cases

  • Code Scan: Identifies hardcoded secrets in source code files.
  • Git History Scan: Detects accidental commits of sensitive information.
  • Token Encryption Verification: Validates proper encryption and storage of tokens.
  • OAuth Security Patterns: Checks for secure OAuth implementations.
  • Webhook Signature Verification: Ensures secure webhook handling.
  • Frontend Secret Exposure: Scans for secrets in frontend code.
  • API Key Security: Verifies secure handling of API keys.
  • Use Case: Before deploying a new version of InsuranceGrokBot, run this Skill to ensure that no sensitive information has been inadvertently exposed.

Quick Start

Run the env-secrets-scan skill to scan the InsuranceGrokBot codebase for potential secrets.

Frequently Asked Questions about env-secrets-scan

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

FAQPage Schema
How do I scan git history for accidentally committed secrets?

To scan git history for accidentally committed secrets, run env-secrets-scan to detect sensitive information in previous commits and ensure secure handling of tokens. It utilizes bash and grep to identify potential leaks.

What is the best way to check for hardcoded API keys in source code?

Checking for hardcoded API keys in source code is done by scanning source files for common secret patterns. This skill verifies secure handling of API keys and identifies sensitive information in templates.

Can I verify OAuth security patterns and webhook signatures using a script?

You can verify OAuth security patterns and webhook signatures using this skill's scripts. It checks for secure OAuth implementations and ensures secure webhook handling by validating proper encryption of tokens.

Does secret detection work for frontend code and templates?

Secret detection works for frontend code and templates by scanning for exposed sensitive information. The skill scans source code and templates to ensure no sensitive data is inadvertently exposed before deployment.

Do I need knowledge of common secret patterns to run a code audit?

You need knowledge of common secret patterns and secure coding practices to effectively run a code audit with this skill. It utilizes grep and bash for detection, requiring familiarity with how secrets are structured.

Why should I scan for sensitive data protection before deploying InsuranceGrokBot?

You should scan for sensitive data protection before deploying InsuranceGrokBot to ensure no sensitive information has been inadvertently exposed. This prevents secret leaks by validating token encryption and API key security.