cc-scout-security

Audit repository security posture across configuration, secrets, dependencies, and tooling.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/z23cc/cc-code --skill cc-scout-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-scout-security
Source: https://github.com/z23cc/cc-code/tree/main/skills/cc-scout-security
Command: npx skills add https://github.com/z23cc/cc-code --skill cc-scout-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables quick assessment of a repository's security posture by auditing configuration, secrets exposure, dependencies, and scanner setups, without performing code changes.

Core Features & Use Cases

  • Configuration & governance audit: branch protection, CODEOWNERS, required checks, and access controls.
  • Secrets & dependency hygiene: detect exposed secrets and identify outdated or vulnerable dependencies.
  • Tooling visibility: summarize security scanning configurations and CI integrations to inform remediation plans.
  • Use Case: security reviews for new repos, pre-merge checks, and ongoing governance audits.

Quick Start

Run the Security Scout audit to surface configuration issues and remediation guidance.

Frequently Asked Questions about cc-scout-security

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

FAQPage Schema
How do I audit repository security posture across branch protection and dependencies?

To audit repository security posture, this Skill reviews branch protection, CODEOWNERS, required checks, and access controls to surface misconfigurations, exposed secrets, and insecure dependencies, generating a structured report with remediation recommendations.

What is checked during a repository security audit for exposed secrets and tooling?

A repository security audit checks configuration, secrets exposure, dependency hygiene, and scanner setups. It detects exposed secrets, identifies vulnerable dependencies, and summarizes security scanning configurations to inform remediation plans.

How do I run a security review for new repos to detect insecure dependencies?

Run the security audit to detect insecure dependencies and configuration issues. It assesses project-level code repositories and CI configurations without performing code changes, outputting remediation guidance for new repo security reviews.

Can I use this security audit for pre-merge checks and ongoing governance audits?

Yes, you can use the security audit for pre-merge checks and ongoing governance audits. It audits repository settings, CODEOWNERS, and scanning tools to produce a structured report highlighting misconfigurations and insecure dependencies.

Does the repository security audit require access to CI configurations and scanning tools?

Yes, the repository security audit requires access to repository settings, CODEOWNERS, and scanning tools. It applies to project-level code repositories and CI configurations to surface misconfigurations and exposed secrets.

What is the best way to surface misconfigurations in repository access controls and CODEOWNERS?

The best way to surface misconfigurations is running the security audit, which reviews branch protection, CODEOWNERS, required checks, and access controls, producing a structured report and remediation recommendations without performing code changes.