secret-scanning

Detect and prevent leaked credentials in GitHub repositories with secret scanning.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tamago0224/kuroshio-mta --skill secret-scanning-tamago0224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-scanning
Source: https://github.com/tamago0224/kuroshio-mta/tree/main/.agents/skills/secret-scanning
Command: npx skills add https://github.com/tamago0224/kuroshio-mta --skill secret-scanning-tamago0224

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams detect, block, and remediate secrets accidentally committed to Git repositories, preventing credential leaks, reducing incident response time, and avoiding downstream service compromise.

Core Features & Use Cases

  • Enable secret scanning & push protection: step-by-step guidance to turn on repository, organization, or enterprise secret protection and push protection.
  • Custom pattern creation and dry runs: define regex-based patterns at repo/org/enterprise scope, dry-run against sample repositories, and publish with optional push-protection enforcement.
  • Alert triage and remediation: prioritize by validity status, rotate credentials, dismiss false positives, and optionally remove secrets from Git history with recommended tooling and cautions.
  • Resolve blocked pushes and delegated bypass: command-line and UI workflows to remove secrets, request or grant bypasses, and manage bypass reviewer workflows and expiration.
  • Pre-commit scanning for AI coding agents: instructions to integrate the Advanced Security Copilot plugin for pre-commit secret scans and agent-based remediation guidance.
  • Reference-driven operations: links to push protection, custom patterns, and alerts & remediation references for deep dives and REST API usage.

Quick Start

Use the secret-scanning skill to enable secret scanning and push protection for my GitHub repository, create a custom pattern for internal API keys, and triage any open alerts.

Frequently Asked Questions about secret-scanning

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

FAQPage Schema
How do I enable GitHub secret scanning and push protection for my repository?

To enable GitHub secret scanning and push protection, you can follow step-by-step guidance to turn on protection at the repository, organization, or enterprise level. This prevents credentials from being committed to Git repositories.

How do I create custom regex patterns for secret scanning?

You can create custom regex patterns for secret scanning at the repository, organization, or enterprise scope. The workflow supports running dry runs against sample repositories before publishing with optional push-protection enforcement.

How do I resolve a blocked push caused by push protection?

To resolve a blocked push, use command-line and UI workflows to remove the detected secrets from your commits. You can also request or grant delegated bypasses and manage bypass reviewer workflows and expiration.

What is the best way to triage secret scanning alerts and remediate leaked credentials?

Triage secret scanning alerts by prioritizing them based on validity status, rotating compromised credentials, dismissing false positives, and optionally removing secrets from Git history using recommended tooling.

Does GitHub secret scanning work with pre-commit hooks for AI coding agents?

Yes, GitHub secret scanning integrates with the Copilot Advanced Security plugin to provide pre-commit scanning for AI coding agents, enabling agent-based remediation guidance before secrets are committed.

Can I manage secret scanning alerts using the REST API?

Yes, you can manage secret scanning alerts using the GitHub REST API. Reference-driven operations provide links to alerts and remediation documentation for deep dives into API usage and extended metadata checks.