secret-scanning-integration

Automate GitHub secret scanning configuration and push protection enforcement.

3|3|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill secret-scanning-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-scanning-integration
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/secure/skills/secret-scanning-integration
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill secret-scanning-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Organizations rely on GitHub's secret scanning and push protection, but configuration is often manual, inconsistent, or missing in many repos. This skill provides a ready-made setup and playbook to automate detection, alerts, and remediation for leaked credentials.

Core Features & Use Cases

  • GitHub secret scanning configuration and push protection enablement across repositories
  • Custom regex patterns for organization-specific secrets and non-provider patterns
  • Automated response playbook for triage, rotation, and incident documentation across workflows and PRs

Quick Start

Enable secret scanning and push protection in your GitHub orgs and repos, add organization-specific patterns, and integrate the response playbook into your security workflow.

Frequently Asked Questions about secret-scanning-integration

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

FAQPage Schema
How do I enable GitHub secret scanning and push protection across multiple repositories?

GitHub secret scanning and push protection can be enabled across repositories by automating the configuration to detect and remediate exposed credentials consistently. This skill applies settings across organizations, workflows, pull requests, and CI processes.

Can I use custom regex patterns for secret scanning to detect organization-specific credentials?

Yes, custom regular expressions can be configured for secret scanning to detect organization-specific secrets and non-provider patterns. This allows detection of proprietary credentials that standard provider-based scanning might miss.

Do I need the GitHub CLI installed to automate push protection enforcement?

Yes, the GitHub CLI (gh) is required to automate push protection enforcement and secret scanning configuration. The skill relies on this dependency to interact with your GitHub repositories and organizations.

What is the best way to respond to leaked credentials detected by GitHub secret scanning?

The best way to respond to leaked credentials is by using a structured response playbook for triage, rotation, and incident documentation. This ensures consistent remediation across workflows and pull requests when exposed credentials are detected.

Does GitHub push protection work with CI workflows and pull requests?

Yes, GitHub push protection works with CI workflows and pull requests by integrating detection and remediation hooks directly into those processes. This prevents credential leakage before code is merged or deployed.