Operations · Intermediate

Verified

Automated verification

  • Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
  • Drafting model not recorded.
  • Second-model review: kimi-code/k3.1-pro (no critical or high findings).
  • Verified .
  • Automated checks and AI review only, not human review.
How verification works

Scan repositories for committed local settings secrets

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

Use with BotBento

Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.

  1. On a scheduleDaily repository scan
  2. ThenSearch for committed local settings
  3. ResultSecret exposure report

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.

Prompt to start with

BotBentoRecommended
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.