infisical-pam
Guide for Infisical Privileged Access Manager (PAM) — brokering human and AI-agent access to databases, servers, Kubernetes clusters, and cloud accounts without the connecting party ever seeing a credential, with full session recording and audit. Covers all 13 account types (SSH, PostgreSQL, MySQL, MSSQL, OracleDB, MongoDB, Redis, Kubernetes, AWS IAM, GCP service account, Azure CLI, Windows, Windows AD), the accounts/folders/templates/memberships model, Admin/Connector/Auditor roles, session lifecycle and recording, just-in-time access requests with approvals, account credential rotation, discovery, dependencies, web and CLI access, and agentic access for AI agents via infisical pam agentic access. Use this skill when someone asks about: Infisical PAM, privileged access, session recording, just-in-time database access, brokered SSH access, giving an AI agent database access safely, access requests and approvals for infrastructure, or 'how do I let someone into production without givi
- Installs
- 143
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/infisical/ai-skills --skill infisical-pam- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads infisical-pam automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Infisical Privileged Access Manager (PAM) Guide
You are a setup assistant helping users broker privileged access to infrastructure through Infisical PAM.
The core property: the connecting party never sees the credential. A person or an AI agent connects through Infisical, Infisical holds the real credential and proxies the connection, and every query or command is recorded.
PAM is a separate Infisical product with its own project type (pam). Enterprise feature.
Not this skill
The boundary is who or what is connecting, and whether they see a credential:
| If the user wants... | Use |
|---|---|
| A person or agent to reach a database/server without holding a credential, with recording | this skill |
| An application to fetch a credential and connect itself | infisical-dynamic-secrets or infisical-setup |
| An ephemeral credential handed to a workload | infisical-dynamic-secrets |
| An existing credential rotated on a schedule into secrets | infisical-secret-rotation |
| Approval workflows for secrets, not infrastructure | infisical-access-control |
| To deploy the Gateway that PAM proxies through | infisical-gateway |
The sharpest distinction is PAM versus dynamic secrets. Both give time-bound access, but:
- Dynamic secrets hand a real credential to the consumer. Good for applications and CI, which need to connect themselves.
- PAM never hands over a credential. Infisical proxies the session. Good for humans and AI agents, where you want recording and the ability to terminate mid-session.
If the user says "I want engineers to query production without knowing the password," that is PAM. If they say "my service needs a database credential," that is dynamic secrets.
The four components
Get this model right and the rest follows:
| Component | What it is |
|---|---|
| Account | One database, server, cluster, or cloud account. Holds connection details and credentials |
| Folder | A grouping of accounts by who needs access. Permissions are set here |
| Account Template | The policy applied when connecting: max session duration, reason required, MFA required. Type-specific |
| Membership | Assigns a user, group, or machine identity a role on a folder or account |
The rule to remember: templates define rules, folders define access.
- Accounts in the same folder can use different templates — same team, different rules
- Accounts in different folders can share a template — same rules, different teams
- Folder memberships cascade to every account inside; assign directly on an account only for exceptions
Organize folders by who needs access, not by technology. backend-team is a better folder than
postgres-databases, because permissions live at the folder level.
Roles
| Role | Capabilities |
|---|---|
| Admin | Full control — accounts, folders, sessions, memberships |
| Connector | Launch sessions and connect to accounts |
| Auditor | View audit logs and session recordings |
Machine identities hold these same roles. Connector is the usual choice for an unattended AI agent.
There is also a product-level role split (admin, member) governing who can create Accounts and
Folders at all.
How to use this skill
- Confirm PAM is right — the connecting party must not hold a credential (see the table above)
- Check the Gateway story — PAM proxies through a Gateway; internal targets need one
- Model folders around teams, not technologies
- Create accounts with connection details and credentials
- Pick or create templates for session policy
- Assign memberships at the folder level
- Decide on just-in-time access — standing Connector access, or access requests with approval
- Confirm recording and auditing meet the requirement
Reference files
| File | When to read |
|---|---|
references/accounts-and-access.md | All 13 account types, per-type auth options, folders, templates, memberships, access requests, discovery, dependencies |
references/sessions-and-agents.md | Session lifecycle and states, recording, termination, web vs CLI access, agentic access for AI agents |
Guiding principles
- Never route a credential to the user. The whole value of PAM is that they do not get one. If a user asks how to retrieve the underlying password, explain that PAM deliberately does not expose it.
- PAM needs a Gateway for anything internal. Connections are proxied. See
infisical-gateway. - Folders are the permission boundary. Someone with access to a folder reaches every account in it. That makes folder design a security decision, not an organizational nicety.
- Recording is real-time. Recordings can be reviewed while a session is still active, and an admin can terminate mid-session. Mention this for incident-response scenarios.
- Require a reason and MFA on production templates. They are template settings, cheap to enable, and they are what makes the audit trail meaningful after the fact.
- Agentic access is the right answer for AI agents.
infisical pam agentic access -- <agent>sandboxes the agent and brokers its access; do not suggest putting a connection string in an agent's environment. - Session TTLs are ceilings, not targets. Set the maximum session duration to the shortest thing that lets real work finish.
FAQ
What does the infisical-pam skill do?
Guide for Infisical Privileged Access Manager (PAM) — brokering human and AI-agent access to databases, servers, Kubernetes clusters, and cloud accounts without the connecting party ever seeing a credential, with full session recording and audit. Covers all 13 account types (SSH, PostgreSQL, MySQL, MSSQL, OracleDB, MongoDB, Redis, Kubernetes, AWS IAM, GCP service account, Azure CLI, Windows, Windows AD), the accounts/folders/templates/memberships model, Admin/Connector/Auditor roles, session lifecycle and recording, just-in-time access requests with approvals, account credential rotation, discovery, dependencies, web and CLI access, and agentic access for AI agents via infisical pam agentic access. Use this skill when someone asks about: Infisical PAM, privileged access, session recording, just-in-time database access, brokered SSH access, giving an AI agent database access safely, access requests and approvals for infrastructure, or 'how do I let someone into production without givi
How do I install infisical-pam?
Run npx skills add https://github.com/infisical/ai-skills --skill infisical-pam in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/infisical-pam/ (personal) or .claude/skills/infisical-pam/ (project).
Which AI agents can use infisical-pam?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is infisical-pam safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains infisical-pam?
It is published by infisical in infisical/ai-skills. It has 143 recorded installs.
More from infisical/ai-skills
infisical-api
infisical/ai-skills
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).
infisical-secret-syncs
infisical/ai-skills
Guide for configuring Infisical Secret Syncs to push secrets from Infisical to third-party services. Covers all 48 sync destinations including AWS Secrets Manager, GCP Secret Manager, Azure Key Vault, GitHub, Vercel, HashiCorp Vault, Cloudflare, Snowflake, Databricks, Railway, and more. Use this skill when someone asks about: syncing secrets to AWS/GCP/Azure, pushing secrets to GitHub Actions, Vercel environment variables, secret sync setup, App Connections, mapping behavior, key schemas, initial sync behavior, or 'how do I get my Infisical secrets into [service]'. Not for creating the required App Connection (infisical-app-connections), pulling secrets into an app (infisical-setup), syncing certificates (infisical-pki PKI Syncs), or rotating a credential (infisical-secret-rotation).
infisical-user-setup-guide
infisical/ai-skills
Interactive setup guide for using Infisical as a secret management tool in your projects. Helps users integrate Infisical into local development (CLI), Docker containers (build-time and runtime secret injection), CI/CD pipelines (GitHub Actions, GitLab CI), Kubernetes (Operator + CRDs), and application code (all 9 SDKs: Node.js, Python, Go, Java, .NET, Ruby, PHP, Rust, C++). Also walks through choosing and configuring any of the 13 machine identity auth methods (Universal, Token, Kubernetes, GCP, AliCloud, AWS, Azure, TLS Cert, OCI, OIDC, JWT, LDAP, SPIFFE). Use this skill whenever someone asks about: using Infisical, injecting secrets, infisical run, infisical init, connecting their app to Infisical, Docker secrets, Kubernetes secrets operator, machine identity setup, SDK initialization, CI/CD secret injection, or 'how do I get my secrets into my app'. Not for the Kubernetes Operator CRDs (infisical-kubernetes-operator), rendering secrets to files (infisical-agent), pushing secrets ou
infisical-agent
infisical/ai-skills
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: Infisical Agent, agent config file, agent templates, rendering secrets to files, sidecar secret injection, init container secrets, token renewal, infisical agent command, or 'how do I use the Infisical Agent to inject secrets'. Not for Kubernetes Secrets or ConfigMaps managed by a controller (infisical-kubernetes-operator), nor infisical run (infisical-setup).
infisical-dynamic-secrets
infisical/ai-skills
Guide for configuring Infisical Dynamic Secrets — on-demand, short-lived credentials for databases, cloud IAM, SSH, and Kubernetes. Covers all 30 providers including PostgreSQL, MySQL, MSSQL, Oracle, Redis, AWS ElastiCache, AWS MemoryDB, MongoDB, Elasticsearch, Couchbase, Milvus, AWS IAM, GCP IAM, Azure Entra ID, SSH certificates, Kubernetes service accounts, LDAP, GitHub, Tailscale, IBM API Connect, and TOTP. Use this skill when someone asks about: dynamic secrets, ephemeral database credentials, short-lived tokens, rotating database users, dynamic PostgreSQL/MySQL/Redis credentials, SSH certificates, temporary AWS IAM users, lease renewal, or 'how do I generate temporary credentials with Infisical'. For brand-new short-lived credentials created per request. Not for changing an existing credential on a schedule (infisical-secret-rotation), nor for recorded human/agent access without a credential (infisical-pam). Covers SSH certificates; TLS certificates are infisical-pki.
infisical-self-host
infisical/ai-skills
Deploy and operate Infisical self-hosted instances with Docker, Docker Compose, and Kubernetes. Covers architecture, environment variables, ENCRYPTIONKEY management, PostgreSQL setup, Redis configuration (including the required noeviction policy), production hardening, FIPS 140-3 compliance, scaling, and high availability patterns. For deploying the Infisical platform itself. Not for the Kubernetes Operator, which is a separate Helm chart (infisical-kubernetes-operator), nor for using Infisical once running (infisical-setup).
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.