What problem does it solve?
Exposed secrets, credentials, and API keys in codebases create serious security risks. This Skill detects sensitive data such as AWS keys, GitHub tokens, Stripe keys, and private keys to prevent leakage and potential compromise. It explicitly notes that it should not be used for code vulnerability scanning (/endor-sast) or dependency checks (/endor-sca).
Core Features & Use Cases
- Secret types detected include AWS Access Key, AWS Secret Key, GitHub Token, GitLab Token, Slack Token, Stripe Key, Google API Key, Private Key, Database URL, JWT Secret, and common publishing tokens.
- Workflow supports running a secrets scan via the MCP tool, reviewing findings, and providing remediation guidance such as rotating secrets and moving to environment-based storage.
- Use case example: a repository accidentally commits a secret; scan, identify, rotate, and implement safeguards to prevent future leakage.
Quick Start
Run a secrets scan on your project with the MCP tool and review the results.