What is credential-scan?

A security command that searches Git history and current project files for exposed credentials such as API keys, tokens, passwords, and private certificates. Git history records older versions of files and commits.

Use it to scan recent Git commits and supported source or configuration files, identify where a credential appears, and receive steps for rotating and removing it.

Credentials can remain exposed even after they are removed from the latest files. Scanning both current files and past commits helps locate leaks that should be revoked and cleaned up.

credential-scan — Command for Claude Code by gonzalezpazmonica

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspace

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/credential-scan/github.svg)](https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/credential-scan)

Your own site

<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/credential-scan"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/credential-scan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/credential-scan"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/credential-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 541 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.00541
Opus 5	$0.00014	$0.00270
Sonnet 5	$0.00006	$0.00108
Haiku 4.5	$0.00003	$0.00054

Measured 6d ago against content hash 9a6ae490fc4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

credential-scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to credential-scan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/credential-scan.md · 72 lines

What it actually says

/credential-scan

Escanea el historial de commits del repositorio buscando credenciales filtradas accidentalmente.

Flujo

1. Banner inicio

╔══════════════════════════════════════╗
║  🔑 Credential Scan                 ║
╚══════════════════════════════════════╝

2. Escanear historial

Patrones a buscar (últimos 50 commits):

git log -50 --all -p | grep -nE \
  'password\s*=\s*["\x27][^"\x27]{8,}|api[_-]?key\s*=\s*["\x27]|token\s*=\s*["\x27][^"\x27]{20,}|-----BEGIN (RSA|DSA|EC|OPENSSH) PRIVATE KEY-----|AKIA[0-9A-Z]{16}|ghp_[a-zA-Z0-9]{36}|sk-[a-zA-Z0-9]{48}'

3. Escanear ficheros actuales

grep -rn "$PATTERNS" \
  --include="*.{cs,ts,js,py,go,rs,php,rb,java,json,yaml,yml,env}" .

Excluir: *.example, *.template, node_modules/, .git/

4. Formato de resultados

🔑 Credential encontrada:
  Tipo: {API key|password|token|private key}
  Ubicación: {fichero}:{línea} (commit: {hash corto})
  Riesgo: 🔴 ALTO — rotar inmediatamente

5. Recomendaciones

Si se encuentran credenciales:

Rotar las credenciales comprometidas inmediatamente
Usar git filter-branch o BFG Repo-Cleaner para limpiar historial
Mover a vault o config.local/ (git-ignorado)

6. Banner fin

╔══════════════════════════════════════╗
║  ✅ Credential Scan — Completo      ║
╚══════════════════════════════════════╝
📄 Reporte: output/credential-scans/YYYYMMDD-scan-{proyecto}.md
⚡ /compact

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 72 lines · 28 tokens per session scan A 9a6ae490fc4d

Subscribe to this mod's changes

credential-scan is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 541 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to credential-scan, differing in 0 lines, and is treated as a copy.

Commits Git and workflow Security

credential-scan