AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Secret Scanner

skill-bestdeejay-design-agent-skills-secret-scanner · by bestdeejay-design

Static secret/token scanning for codebases and git repos: detects leaked credentials (AWS, GitHub, OpenAI, Anthropic, Stripe, Google, Slack, private keys, JWTs) using gitleaks v8.30.1 pattern table + Shannon entropy gating + allowlist noise filters. Stdlib-only Python script with JSON/Markdown/text reports, redaction, CI exit-code gate.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-bestdeejay-design-agent-skills-secret-scanner

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-bestdeejay-design-agent-skills-secret-scanner)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Secret Scanner? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Secret Scanner — leaked credential detection

Load this skill when you need to scan a codebase, directory, or git repo for leaked secrets/tokens/keys (before publishing a repo, before a release, or during security review).

The scanner is static and offline by design: patterns come from the gitleaks v8.30.3 default config, the canonical open-source secret-detection rule set, and detection uses the same Shannon-entropy gating semantics as gitleaks. No network calls are made — a format match is reported as potential, not verified.


The scanner script

scripts/secret_scanner.py — pure Python 3 stdlib (no dependencies).

| Source | Command | |---|---| | File | python3 secret_scanner.py --path path/to/file | | Directory (recursive) | python3 secret_scanner.py --path path/to/dir | | Git repo (tracked files) | secret_scanner.py --git /path/to/repo | | stdin (blob) | cat file | secret_scanner.py |

Detected pattern families (19 rules)

Critical: AWS Access Key ID (AKIA/ASIA/ABIA/A3T…) & secret key, GitHub PAT classic/fine-grained/refresh tokens, OpenAI (sk-*T3BlbkFJ*), Anthropic (sk-ant-api03-…AA), Stripe (sk_live_/rk_live_), Google API key (AIza…), private keys (PEM/OpenSSH/PGP blocks). High: Slack app/bot/user tokens and webhooks, Perplexity (pplx-…). Medium: JWT, generic keyword-anchored API keys.

False-positive suppression (allowlists)

  • Placeholders: $VAR, ${VAR}, {{ }}, %VAR%, true/false/null,

****, EXAMPLE, xxxx, your-, placeholder, TODO — never reported

  • Noise paths: node_modules/, vendor/, .git/, lockfiles

(package-lock.json, go.sum, poetry.lock, …), minified JS, binaries, images, fonts

  • Entropy gate: every entropy-sensitive rule skips values whose Shannon

entropy ≤ rule minimum (gitleaks semantics)

Capabilities

  • --json / --markdown / text (default) report formats
  • --redact N — mask secrets in output (keeps first N chars; CI-safe)
  • --max-mb N — skip huge files (default 10 MB)
  • --exit-code — exit 1 when findings present (CI gate), else 0

Usage example (typical)

# Full directory scan, JSON report for CI
python3 secret_scanner.py --path ./my-repo --json --redact 8 --exit-code

# Scann only tracked files of a repo
python3 secret_scanner.py --git /Users/me/projects/lovii_demo

# Markdown human-readable report
python3 secret_scanner.py --path ./app --markdown > scan-report.md

Interpretation guidance

  • Critical + live risk (AWS/GitHub/OpenAI/Anthropic/etc.) → rotate the

credential first, then scrub history. Assume a committed secret is compromised (forks, cache, CI logs, bots).

  • Medium (generic/JWT) → verify context before alarming; check whether the

value appears in tests/fixtures/docs.

  • Allowlisted but suspicious → check if .env.example contains a real key

instead of a YOUR_KEY placeholder.

  • Only the operator can confirm whether a secret is still live — offline

heuristic check (token length/grammar, EXAMPLE suffix) is automatic.

Canonical patterns

Full deep dive with upstream sources in references/canonical-patterns.md. Key canons:

  • gitleaks rule table (v8.30.3 config/gitleaks.toml) — the canonical regex

set; entropy per-rule minimums

  • Shannon entropy gatingdetect/utils.go#L117-L134; skip when

entropy AnalogWhat we borrow gitleaks (GitHub, MIT)Pattern table, entropy thresholds, global/path allowlists, redaction, exit-code CI model TruffleHog v3Typed-detector philosophy; verified vs unverified` framing (we stay offline) Yelp detect-secretsQuoted-string scanning to cut noise; keyword-anchored entropy NVIDIA SkillSpectorTwo-stage analysis; severity scoring; false-positive baseline/suppression

Installation

# For opencode
cp -r skills/secret-scanner ~/.config/opencode/skills/

# For other agents
# Copy the skill folder to your skills directory; requires Python 3.

> Security note: this tool finds potential secrets. It never comments > them out, does not attempt to "verify" them online, and never rewrites > source files. Operators must rotate real secrets and scrub history > manually — see references/canonical-patterns.md → Remediation workflow.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.