skills.rest
lookatitude
lookatitudeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

security-secrets-scan

Scan git history and build artifacts for leaked credentials and tokens.

6|Updated Apr 24, 2026
Search Tags:#pre-commit#ci-cd#security-audit#git-history#secrets-management#secret-scan#credential-rotation
One-click install
npx skills add https://github.com/lookatitude/guild --skill security-secrets-scan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-secrets-scan
Source: https://github.com/lookatitude/guild/tree/main/skills/specialists/security-secrets-scan
Command: npx skills add https://github.com/lookatitude/guild --skill security-secrets-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans repository history and build artifacts for leaked secrets (keys, tokens, certs) and proposes a prevention policy — pre-commit hooks, CI check, rotation plan. Output: findings report, remediation steps (rotate / revoke / invalidate), and hook/CI proposals. Pulled by the security specialist. TRIGGER: "scan the repo for leaked secrets", "check for exposed API keys in X", "secret-scan the X artifact", "audit git history for credentials", "find leaked tokens in X", "set up leak-prevention hooks for X".

Core Features & Use Cases

  • Scan history and build artifacts for leaked credentials, tokens, and certificates.
  • Verify findings, rotate secrets to stop live use, and land prevention (pre-commit hooks + CI checks).
  • Triage false positives with an allowlist and establish escalation for confirmed live secrets.

Quick Start

Run the security-secrets-scan on your repository to generate a findings report and remediation plan.

Frequently Asked Questions about security-secrets-scan

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

FAQPage Schema
How do I scan git history for leaked secrets and credentials?▼

Scanning git history for leaked secrets involves analyzing repository commits and build artifacts to surface exposed API keys, tokens, and certificates, generating a detailed findings report with remediation steps.

What is the best way to set up pre-commit hooks to prevent exposed API keys?▼

Preventing exposed API keys via pre-commit hooks is achieved by implementing proposed CI checks and local hooks that scan credentials before they are committed, establishing a continuous leak-prevention policy.

How do I triage false positives when checking for exposed tokens in build artifacts?▼

Triaging false positives when checking for exposed tokens requires configuring an allowlist to filter out non-sensitive matches, ensuring only confirmed live secrets trigger escalation and credential rotation procedures.

Can I audit git history for credentials across all past commits?▼

Auditing git history for credentials across all past commits is supported by running a comprehensive secret-scan that traverses historical changes and build outputs to detect leaked certificates and tokens.

Do I need to manually rotate secrets after a security audit finds leaked tokens?▼

Following a security audit that finds leaked tokens, you must execute the provided remediation steps to rotate or revoke the compromised credentials, stopping live use before deploying prevention hooks.

Related Skills

Explore More Software Engineering Skills→
Kalp1774Kalp1774
18

secrets

Scan files, endpoints, and repositories for exposed secrets and credentials.

Community
Intermediate
Camilo8902Camilo8902

secrets-scanner

Detect leaked credentials in code repositories with Gitleaks, detect-secrets, and TruffleHog.

Community
Advanced
MayaDispelerMayaDispeler
3

devsecops

Apply security checks across CI/CD pipelines with GitLeaks, Semgrep, Snyk, Trivy, and cosign.

Community
Advanced
x-cmdx-cmd
4.6k

security-review

Automate security audits for code changes using native shell tools.

Official
Intermediate