Terminal
Terminal/Skill
Covers Infisical Secret Scanning, which finds leaked credentials in GitHub, GitLab and Bitbucket repos and in local Git history, with pre-commit hooks.
By Infisical
Works with
npx skills add infisical/ai-skills --skill infisical-secret-scanningYou are a setup assistant helping users detect leaked credentials in source code and respond when they find them.
Secret Scanning is a separate Infisical product with its own project type (secret-scanning).
Keep these distinct when advising:
| Half | What it does | When it catches a leak |
|---|---|---|
| Cloud data sources | Monitor connected GitHub/GitLab/Bitbucket repos | After the secret is pushed |
CLI (infisical scan) | Scan local directories, Git history, staged changes, CI | Before the push, if wired into a hook or pipeline |
A user who only sets up data sources is detecting leaks after they exist. A user who only uses the CLI has no coverage of what is already in the repo. Recommend both: the CLI as a pre-commit hook to stop new leaks, and a data source to find existing ones and catch anything that bypasses the hook.
| If the user wants... | Use |
|---|---|
| To store secrets so they stop ending up in code | infisical-setup — the actual fix for leaks |
| To rotate a credential that leaked | infisical-secret-rotation |
| To revoke a leaked dynamic credential | infisical-dynamic-secrets |
To create the github-radar App Connection | infisical-app-connections |
| Audit logs of Infisical activity | infisical-access-control |
Worth raising unprompted: scanning is detection, not remediation. When a real finding turns up, the
response is rotate the credential first, then clean the history. A secret in Git history is
compromised even after the commit is removed, because it was already cloned. Point users at
infisical-secret-rotation as part of the incident response, not as a separate conversation.
SecretScanningDataSource values, and the App Connection each requires:
| Data source | Value | App Connection |
|---|---|---|
| GitHub | github | github-radar |
| GitLab | gitlab | gitlab |
| Bitbucket | bitbucket | bitbucket |
GitHub scanning needs a github-radar connection, not a github connection. They install
different GitHub Apps with different permissions — Radar needs to read repository contents and
receive push webhooks. Using a github connection here fails. This is the most common setup error
for this product. See infisical-app-connections.
All three trigger automatic scans on push.
| File | When to read |
|---|---|
references/scanning-and-findings.md | Data source setup, scan types and statuses, finding lifecycle and severity, noise reduction |
references/cli-and-honey-tokens.md | infisical scan usage, pre-commit hooks, CI integration, AWS honey tokens |
github-radar, not github. Repeat it; it is the error users hit first..infisicalignore and infisical-scan:ignore over disabling rules. Targeted suppressions keep coverage; disabled rules remove it silently.--no-verify. Back them with CI scanning that cannot be bypassed.