secret-scanning

Configure GitHub secret scanning with push protection and custom patterns.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/yao-agent-skills --skill secret-scanning-firstsun-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-scanning
Source: https://github.com/firstsun-dev/yao-agent-skills/tree/main/external/develop/security/secret-scanning
Command: npx skills add https://github.com/firstsun-dev/yao-agent-skills --skill secret-scanning-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Secret scanning helps prevent the leakage of credentials by detecting exposed secrets across repositories and during pushes, enabling timely remediation and policy enforcement.

Core Features & Use Cases

  • Detects exposed credentials across repo history, commits, issues, and comments
  • Enables push protection, custom patterns, alert triage, and remediation workflows
  • Supports pre-commit scanning via the GitHub MCP Server with the Advanced Security plugin for AI-assisted workflows

Quick Start

Enable secret scanning and push protection on your repository, then define a custom pattern to block secrets.

Frequently Asked Questions about secret-scanning

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

FAQPage Schema
What is GitHub secret scanning and how does it prevent exposed credentials?

GitHub secret scanning detects exposed credentials across repository history, commits, issues, and comments to prevent leakage. It enables timely remediation and policy enforcement by identifying secrets before they are exploited.

How do I enable push protection and configure custom patterns for secret scanning?

Push protection and custom patterns are configured by enabling secret scanning on your repository or organization. You then define specific custom patterns to block designated secrets from being pushed to the repository.

Can I use pre-commit scanning with the GitHub MCP Server for AI-assisted workflows?

Pre-commit scanning is supported via the GitHub MCP Server with the Advanced Security plugin. This integration enables AI-assisted workflows to detect and block exposed secrets before they enter the repository history.

Does GitHub secret scanning work for organizations and triage alert remediation?

Secret scanning applies to repositories and organizations, supporting alert triage and remediation workflows. It detects leaked credentials across the organization and facilitates timely remediation to enforce security policies.

What is the best way to manage secret scanning alerts and remediation workflows?

The best way to manage secret scanning alerts is to enable detection across your repositories and use the triage and remediation workflows. This approach identifies exposed credentials and facilitates timely remediation to enforce security policies.