Canonical: https://botbento.com/usecases/scan-repositories-for-committed-local-settings-secrets/
Format: Markdown representation of the public HTML page.

# Scan repositories for committed local settings secrets

[Operations](https://botbento.com/usecases/ops/) · Intermediate

Find credential-bearing config files in source control before they spread

Review repositories for local coding-agent settings files that were committed by mistake and may contain approved commands with embedded credentials. Triage each match, redact sensitive values, and prepare a report so maintainers can remove exposure and add ignore rules.

## Quick answers

**What does it do?** Find credential-bearing config files in source control before they spread. Result: Secret exposure report.

**What does it need?** Tools: GitHub, Slack, Terminal. Intermediate: some setup. The prompt includes an approval step.

**How do I run it?** On a schedule: Daily repository scan. Copy the prompt below into a bot in BotBento.

## How it works

1. On a schedule: Daily repository scan
2. Then: Search for committed local settings
3. Result: Secret exposure report

## Prompt to start with

```text
On a daily schedule, search the approved GitHub organization for committed local settings files used by coding agents. Inspect matches for command strings that appear to contain passwords, tokens, keys, or other credentials. Redact secret values in all notes and reports, and rank findings by likely exposure and ease of remediation. Produce a report listing repository, file path, risk summary, and suggested cleanup steps. Wait for user approval before sending alerts, posting to channels, making purchases, deleting files, rewriting history, changing repository settings, or contacting maintainers. Never commit changes without explicit approval.
```

## Tools it uses

GitHub, Terminal, Slack

## Works with

BotBento

## Tags

security, secrets, github, scanning, repo-hygiene

## Source

[Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files](https://news.ycombinator.com/item?id=50407882) — Hacker News · checked 2026-11-13

Summarized in our own words. Any results described there are the authors’ own, not measured by BotBento.

Verified 2026-11-13: passed every automated gate and a second-model review (kimi-code/k3.1-pro). Automated, not human review. [How verification works](https://botbento.com/usecases/verification/)

By BotBento Editorial · Added 2026-11-13 · Updated 2026-11-13 · [Suggest a correction](https://botbento.com/contact/)

## Related use cases

- [Vet third-party AI tool packages before installation](https://botbento.com/usecases/vet-third-party-ai-tool-packages-before/) — Compare declared capabilities with actual files and probe risky servers.
- [Track reuploads of a codebase on GitHub and draft takedown notices](https://botbento.com/usecases/track-reuploads-of-a-codebase-on-github/) — Scan GitHub for repositories that reuse shipped code, then queue notices
- [Scheduled trusted root certificate store audit](https://botbento.com/usecases/scheduled-trusted-root-certificate-store-audit/) — Flag unexpected root CAs before they weaken TLS trust
