endor-secrets

Scan codebases and identify exposed secrets, credentials, and API keys with remediation steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan and identify exposed secrets, credentials, API keys, and other sensitive data hidden in codebases, enabling quick remediation and secure coding practices.

Core Features & Use Cases

  • Secret pattern detection: Detects tokens, keys, and credentials across languages and repositories.
  • Automated remediation guidance: Provides steps to rotate keys and remove secrets from code.
  • Use Case: In a multi-repo project, quickly locate secrets in source files, review findings, and implement safe replacements.

Quick Start

Start a secrets scan with the Endor MCP workflow in Claude Code or via the /endor-scan command to detect exposed secrets and receive remediation guidance.

Frequently Asked Questions about endor-secrets

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 source code?

Secret scanning analyzes codebases and CI pipelines to identify exposed credentials, API tokens, and private keys. It validates findings against known secret patterns and returns structured results with remediation guidance.

How do I scan for credentials across multiple repositories?

You can scan for credentials across multiple repositories by targeting multi-language projects and CI pipelines. The scan detects sensitive data like API keys and returns structured results to help you locate and review findings across your codebase.

Does secret scanning work with pull requests and CI pipelines?

Yes, secret scanning targets pull requests and CI pipelines to identify exposed credentials and API keys. It validates detected patterns and provides structured results to ensure sensitive data is caught before merging.

What should I do after detecting exposed API tokens in my code?

After detecting exposed API tokens, you should follow the suggested remediation steps to rotate keys and remove secrets from the code. The scan provides structured findings to help you implement safe replacements and secure your codebase.

What types of sensitive data can static analysis detect in a codebase?

Static analysis can detect sensitive data in a codebase including API tokens, private keys, and credentials. It targets patterns across multi-language source files and CI pipelines to locate and validate exposed secrets.