Skip to content
TakoAPI
Back to skills

ggshield-scanner

by amascia-gg

Security & Passwords
2.1kDownloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Detect 500+ types of hardcoded secrets.

Description

What This Skill Does

Wraps GitGuardian's ggshield CLI to scan repositories, files, staged changes, and Docker images for 500+ types of hardcoded secrets. It can install git pre-commit hooks to automatically block commits containing credentials before they reach version control.

ggshield combines entropy analysis, known-format pattern matching, and ML trained on real leaked credentials, catching secrets that simple regex scanners miss.

When to Use It

  • Scan a repo for leaked API keys before pushing to GitHub
  • Audit an old project for credentials accidentally committed to history
  • Block commits containing hardcoded secrets via pre-commit hooks
  • Check a Docker image for secrets embedded in its layers
  • Add automated secret detection to a CI/CD pipeline

Example Workflow

INPUT

User asks: scan my repo for secrets before I push

AGENT
  1. 1

    Runs scan-repo on the target repository path

  2. 2

    ggshield scans all files and git history for secret patterns

  3. 3

    Identifies matches by file path and line number

  4. 4

    Returns a clean confirmation or a list of detected secrets with remediation advice

OUTPUT

Found 2 secrets: AWS Access Key ID in config/prod.py:42, Slack API token in .env.backup:8. Rotate these credentials immediately and remove them from history.

Requirements

  • GitGuardian account (free at dashboard.gitguardian.com)
  • GITGUARDIAN_API_KEY environment variable set to your API key
  • ggshield CLI installed

Installation

clawhub install amascia-gg/ggshield-scanner

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links