security-protocol

Enforce environment-variable isolation and detect leaked credentials in repositories.

1|Updated Apr 18, 2026

Search Tags:#git #security #authentication #compliance #encryption #secrets

Ready to run

npx skills add https://github.com/CC90210/CMO-Agent --skill security-protocol-cc90210

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-protocol
Source: https://github.com/CC90210/CMO-Agent/tree/main/skills/security-protocol
Command: npx skills add https://github.com/CC90210/CMO-Agent --skill security-protocol-cc90210

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git-filter-repo, and includes scripts (resource) components.

What problem does it solve?

This skill prevents the accidental exposure of sensitive API keys, tokens, and credentials by enforcing strict environment-based configuration and automated security scanning.

Core Features & Use Cases

Credential Hardening: Ensures all secrets are stored in gitignored environment files rather than hardcoded in scripts or configuration files.
Automated Security Audits: Provides a robust scanning tool to detect leaked credentials in the working tree or commit history before they are pushed to remote repositories.
Incident Response: Offers a standardized protocol for rotating compromised keys and scrubbing sensitive data from version control history.

Quick Start

Run the security protocol scanner to check the current repository for any exposed API keys or sensitive credentials.

Frequently Asked Questions about security-protocol

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

FAQPage Schema

How do I scan my git repository for leaked API keys and tokens?▼

The scanner detects exposed credentials in your working tree or commit history before you push to a remote repository, identifying hardcoded API keys, tokens, and sensitive configuration files.

How do I remove sensitive data from git commit history after a secret leak?▼

You can scrub sensitive data from git history using the git-filter-repo dependency, which provides a standardized incident response protocol for removing exposed secrets and rotating compromised keys.

Do I need git-filter-repo to enforce environment variable isolation for credentials?▼

Yes, git-filter-repo is required for history scrubbing, while local environment files handle secret storage. The skill enforces environment-variable isolation to ensure secrets are stored in gitignored files rather than hardcoded in scripts.

What is the best way to prevent hardcoded secrets in configuration files?▼

Credential hardening prevents hardcoded secrets by enforcing strict environment-based configuration, ensuring all API keys and tokens are stored in gitignored environment files instead of being exposed in scripts or configuration files.

Does automated security auditing work for already committed sensitive configuration files?▼

Yes, automated security audits detect leaked credentials in both the working tree and commit history. If exposed secrets are found, the incident response protocol uses git-filter-repo to scrub sensitive data from version control.