endor-secrets

Scan codebases for exposed secrets and API keys via MCP.

2|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/endorlabs/skills-ideas --skill endor-secrets-endorlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: endor-secrets
Source: https://github.com/endorlabs/skills-ideas/tree/main/skills/endor-secrets
Command: npx skills add https://github.com/endorlabs/skills-ideas --skill endor-secrets-endorlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about endor-secrets

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

FAQPage Schema
How do I scan a codebase for exposed secrets and API keys?

To scan a codebase for exposed secrets, run a secrets scan via the MCP tool workflow. It identifies hardcoded tokens, private keys, and credentials across multiple file types in repositories, CI pipelines, and local development environments.

What types of hardcoded credentials and tokens can secret scanning detect?

Secret scanning detects AWS Access Keys, AWS Secret Keys, GitHub Tokens, GitLab Tokens, Slack Tokens, Stripe Keys, Google API Keys, Private Keys, Database URLs, JWT Secrets, and common publishing tokens to prevent leakage.

How do I remediate leaked API keys and rotate exposed secrets in my repository?

To remediate leaked API keys, review the scan findings to identify exposed secrets, rotate the compromised credentials, and move sensitive data to environment-based secret management to prevent future leakage.

Does this secrets detection tool also check for code vulnerabilities or dependency issues?

Secrets detection does not check for code vulnerabilities or dependency issues. Use dedicated SAST scanning for code vulnerabilities and SCA scanning for dependency checks, keeping secret detection focused on credential leakage.

Can I scan for hardcoded tokens in CI pipelines and local development environments?

You can scan for hardcoded tokens in CI pipelines and local development environments. The scanning supports multi-file type analysis across repositories to detect sensitive data like database URLs and JWT secrets.

What is the best way to prevent private keys from leaking into source code?

The best way to prevent private keys from leaking is to scan codebases for sensitive data, rotate any found credentials, and implement environment-based secret management to securely store keys outside the source code.