infisical/ai-skills

infisical-secret-scanning

Guide for Infisical Secret Scanning — detecting leaked credentials in source code and developer systems.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/infisical/ai-skills --skill infisical-secret-scanning

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Infisical Secret Scanning Guide

You 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).

Two halves that solve different problems

Keep these distinct when advising:

HalfWhat it doesWhen it catches a leak
Cloud data sourcesMonitor connected GitHub/GitLab/Bitbucket reposAfter the secret is pushed
CLI (`infisical scan`)Scan local directories, Git history, staged changes, CIBefore 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.

Not this skill

If the user wants...Use
To store secrets so they stop ending up in codeinfisical-setup — the actual fix for leaks
To rotate a credential that leakedinfisical-secret-rotation
To revoke a leaked dynamic credentialinfisical-dynamic-secrets
To create the github-radar App Connectioninfisical-app-connections
Audit logs of Infisical activityinfisical-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.

Data sources

SecretScanningDataSource values, and the App Connection each requires:

Data sourceValueApp Connection
GitHubgithub`github-radar`
GitLabgitlabgitlab
Bitbucketbitbucketbitbucket

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.

How to use this skill

  1. Wire the CLI into pre-commit so new leaks are stopped at the source
  2. Connect the data sources for repositories that matter
  3. Run a full scan to establish a baseline of what already exists
  4. Triage findings — resolve, mark false positive, or ignore
  5. Tune to reduce noise so the signal stays credible
  6. Enable automatic diff scans for ongoing coverage
  7. Consider honey tokens for detecting misuse rather than exposure

Reference files

FileWhen to read
references/scanning-and-findings.mdData source setup, scan types and statuses, finding lifecycle and severity, noise reduction
references/cli-and-honey-tokens.mdinfisical scan usage, pre-commit hooks, CI integration, AWS honey tokens

Guiding principles

  • `github-radar`, not `github`. Repeat it; it is the error users hit first.
  • Rotate before cleaning history. A leaked credential is compromised the moment it is pushed. Rewriting history does not un-leak it.
  • False positives destroy the control. A noisy scanner gets ignored, and then a real finding gets ignored too. Invest in ignore rules and entropy tuning early.
  • Prefer `.infisicalignore` and `infisical-scan:ignore` over disabling rules. Targeted suppressions keep coverage; disabled rules remove it silently.
  • Pre-commit hooks are advisory, not enforcement. They can be skipped with --no-verify. Back them with CI scanning that cannot be bypassed.
  • Honey tokens detect a different thing. Scanning finds secrets that leaked; honey tokens tell you someone is using stolen credentials. They complement each other.
  • Never echo a discovered secret value back to the user in full.
from this repository

More skills

All skills
infisical
Community

infisical-access-control

Guide for Infisical access control and governance — org and project roles, custom roles with subject/action permissions, granular secret permissions that separate describing a secret from reading its value, attribute-based access control (ABAC) driven by user metadata and machine identity attributes, additional privileges, assume-privilege, temporary (time-bound) access, access requests, change-approval and access-approval policies, and audit logs including streaming to Splunk, Datadog, Azure, C

1h installs
1
GitHub stars
41
Updated
Nov 11
infisical
Community

infisical-agent

Guide for configuring the Infisical Agent — a client daemon that manages token lifecycle and renders secrets via Go templates without modifying application code. Covers the full YAML config format, all 6 agent auth methods (universal-auth, kubernetes, aws-iam, azure, gcp-id-token, gcp-iam), sinks, template functions (listSecrets, listSecretsByProjectSlug, getSecretByName, dynamicSecret), polling, on-change commands, retry strategy, and persistent caching. Use this skill when someone asks about:

1h installs
1
GitHub stars
41
Updated
Nov 11
infisical
Community

infisical-api

Interact with the Infisical REST API to manage secrets, projects, environments, machine identities, and more. Supports secret CRUD operations, machine identity authentication, pagination, and rate limiting on cloud deployments. Not for the CLI/SDKs (infisical-setup), KMS crypto endpoints (infisical-kms), certificate endpoints (infisical-pki), or human SSO login (infisical-sso).

1h installs
1
GitHub stars
41
Updated
Nov 11
infisical
Community

infisical-app-connections

Guide for creating and managing Infisical App Connections — the reusable authenticated links between Infisical and third-party services that Secret Syncs, Secret Rotations, PKI certificate authorities, PKI Syncs, and Secret Scanning data sources all depend on. Covers all 83 connection types and their exact auth methods (AWS assume-role vs access-key, GitHub OAuth vs GitHub App vs PAT, Azure OAuth vs client-secret vs certificate, GCP service account impersonation, and more), platform-managed cred

1h installs
1
GitHub stars
41
Updated
Nov 11