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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote 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.
[](https://agentmods.dev/commands/gonzalezpazmonica/savia/credential-scan)<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/credential-scan"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/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.
<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/credential-scan"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/credential-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 |
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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- credential-scan — 100% identical, 0 lines differ
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-branchoBFG Repo-Cleanerpara 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
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.
- 3d ago First seen · 72 lines · 28 tokens per session scan A 9a6ae490fc4d
credential-scan is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other commands, from other repositories
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
handoff
Emit a handoff artifact for this session (optionally specify a slug).
smart-commit
Smart batch commit — group changes by cohesion, generate commit messages matching project style, output git commands.
commit
Read this skill before making git commits.
commit
Command "commit" from kylepelham/Drift, covering git diff, git diff --cached and git status --short.