agentleFS
Sign inStart free
kaandgnshkaandgnsh/Claude-Blue/skills/secrets-management/secret-scanning/SKILL.md

secret-scanning

Skill0 starsChanged 14 days agoMITView on GitHub

Detect hard-coded secrets in code, Git history, CI logs, container images and file shares with gitleaks, TruffleHog, GitHub secret scanning and push protection — tuning, verification of live secrets, baselines and pre-commit/CI integration. Use when setting up secret detection, scanning a repository or organization, or triaging secret-scanning alerts.

  • Reads credentials

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Where else?: If it's in history, it's in every clone and fork.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Secret Scanning

Tools

gitleaks git -v --report-format sarif --report-path gitleaks.sarif .        # full history (gitleaks v8.19+ subcommands; older: gitleaks detect)
gitleaks dir ./config                                                        # files without git
trufflehog git file://. --results=verified,unknown                          # verifies credentials against providers
trufflehog github --org=my-org --results=verified                            # org-wide (needs token)
trufflehog docker --image ghcr.io/org/app:1.4.2

Pre-commit hook (.pre-commit-config.yaml):

repos:
  - repo: https://github.com/gitleaks/gitleaks
    rev: v8.24.0
    hooks:
      - id: gitleaks

GitHub: enable secret scanning + push protection org-wide; add custom patterns for internal token formats; validity checks for supported partners.

Triage

  1. Live? Verified/valid secrets are P1 → secret-leak-response.
  2. Real or test? Example keys (AKIAIOSFODNN7EXAMPLE), fixtures, placeholders → allowlist precisely (.gitleaks.toml [allowlist] with paths/regexes, or # gitleaks:allow inline).
  3. Where else? If it's in history, it's in every clone and fork.
  4. Owner from git log -S'<fragment>' --all / blame.

Coverage beyond Git

CI logs and artifacts, container image layers, IaC state files (terraform.tfstate often holds plaintext secrets), wikis/Confluence, Slack/Teams exports, S3 buckets, endpoint config files (.env, .npmrc, .aws/credentials).

Metrics

New secrets per month, mean time to revoke, push-protection bypasses (review each), repos without scanning.

Related skills

secret-leak-response, ci-secret-review, source-control-hardening, release-gate

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free