cm-secret-shield

Enforces defense-in-depth security for AI-assisted development pipelines.

48|23|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/tody-agent/codymaster --skill cm-secret-shield
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-secret-shield
Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-secret-shield
Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-secret-shield

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defense-in-depth security to prevent secrets leakage across the full AI-assisted development lifecycle, from writing code to deployment and runtime.

Core Features & Use Cases

  • Layered protection across five defense layers (Write Guard, Pre-Commit Guard, Repo Scan, Deploy Gate, Runtime Guard) to stop secrets at the source.
  • Automated checks via pre-commit hooks, repository scans, and deploy-time audits, with integration points to cm-project-bootstrap and cm-safe-deploy.
  • Rotation tracking and secret lifecycle governance to ensure timely key rotation and traceability.

Quick Start

Install and enable the pre-commit guards to automatically scan for secrets before every commit.

Frequently Asked Questions about cm-secret-shield

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

FAQPage Schema
How do I prevent secrets from leaking in AI-assisted code?

Preventing secrets from leaking in AI-assisted code requires defense-in-depth security across the development lifecycle. Automated guardrails block leaks by enforcing checks during code writing, pre-commit hooks, repository scans, and pre-deploy audits.

How do I set up pre-commit hooks for secret scanning?

Setting up pre-commit hooks for secret scanning involves installing and enabling the Pre-Commit Guard. This automatically scans staged files to block secrets before every commit, stopping leaks at the source.

What is defense-in-depth security for secret management?

Defense-in-depth security for secret management is a layered protection strategy covering five defense layers: Write Guard, Pre-Commit Guard, Repo Scan, Deploy Gate, and Runtime Guard. These layers stop secrets at the source across ongoing development.

Does this secret scanning approach work with existing deployment workflows?

This secret scanning approach works with existing deployment workflows through a Deploy Gate. It integrates with cm-project-bootstrap and cm-safe-deploy workflows to perform deploy-time audits and prevent leaked secrets from reaching production.

Can I track secret rotation and lifecycle governance automatically?

You can track secret rotation and lifecycle governance automatically using the Runtime Guard. It ensures timely key rotation and traceability across new projects and ongoing development, satisfying layered safety guardrail requirements.

What is the best way to scan an entire git repository for secrets?

The best way to scan an entire git repository for secrets is using the Repo Scan defense layer. It performs repository-wide audits to detect hidden secrets, complementing pre-commit hooks and deploy-time checks for full lifecycle coverage.