skills.rest
neuron-one
neuron-oneCOMMUNITY
Explore all skills by this author →
GitHub

secrets-guard

Identify exposed secrets in code repositories and git history.

25|10|Updated Apr 1, 2026
Search Tags:#security#codebase#secrets#credentials#static-analysis#git-history#env-files
One-click install
npx skills add https://github.com/neuron-one/GODMODE --skill secrets-guard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets-guard
Source: https://github.com/neuron-one/GODMODE/tree/main/skills/security/secrets-guard
Command: npx skills add https://github.com/neuron-one/GODMODE --skill secrets-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finds exposed secrets, API keys, tokens, and credentials in codebases to prevent accidental leaks across environments.

Core Features & Use Cases

  • Hardcoded Secrets in Code: searches for patterns like API keys, JWT secrets, tokens, and private keys.
  • Environment Files & Git History: scans .env files and historical commits to surface hidden credentials.
  • Configuration Files & Output: analyzes config files and provides a structured, actionable report with remediation guidance.

Quick Start

Scan a repository for exposed secrets and report findings.

Frequently Asked Questions about secrets-guard

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

FAQPage Schema
How do I find exposed secrets and API keys in my codebase?▼

You can scan for exposed secrets by applying static analysis to your codebase, using pattern matching to detect hardcoded API keys, tokens, and credentials across source code and configuration files.

Can I scan git history for leaked credentials in previous commits?▼

Yes, you can scan git history to surface hidden credentials left in previous commits. This process checks historical records alongside current code and .env files to generate a report with remediation steps.

Does secrets-guard work for CI pipelines and automated code audits?▼

Yes, this approach applies to CI pipelines and code audits. It identifies exposed secrets across codebases and histories, outputting a structured findings report with remediation guidance suitable for automated security checks.

What is the best way to detect hardcoded private keys and JWT secrets in source code?▼

The best way to detect hardcoded private keys and JWT secrets is using pattern matching static analysis. This technique scans source code and config files for specific key formats, delivering a structured report detailing the exposed credentials and their remediation steps.

How do I get remediation guidance after finding exposed tokens in my repository?▼

After finding exposed tokens, you get remediation guidance by reviewing the structured findings report generated by the scan. This report details the identified credentials and provides actionable steps to resolve the security vulnerabilities across your codebase.

Related Skills

Explore More Software Engineering Skills→
emliunixemliunix

privacy-review

Scan Git repositories for exposed secrets and sensitive data.

Community
Advanced
Clear-CapabilitiesClear-Capabilities
73

agentic-security:security-rotate-leak

Rotate leaked API keys and credentials end-to-end across supported providers.

Official
Advanced
achmfachmf

vulnerability-scanner

Scan software projects for vulnerabilities, hardcoded secrets, and insecure code patterns.

Community
Advanced
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced