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 auth methods (Universal Auth, Kubernetes, AWS IAM, Azure, GCP ID Token, GCP IAM), sinks, template functions (listSecrets, listSecretsByProjectSlug, getSecretByName, dynamicSecret), polling, on-change commands, and caching. Use this skill when someone asks about: Infisical Agent, agent config file, agent templates, rendering secrets to files, sidecar secret injection, token renewal, infisical agent command, or 'how do I use the Infisical Agent to inject secrets'.
How do I install this agent skill?
npx skills add https://github.com/infisical/ai-skills --skill infisical-agentIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides technical documentation and configuration guidance for the Infisical Agent, a tool designed for secret lifecycle management and automated secret injection using Go templates. It covers various authentication methods, deployment scenarios, and template functions, describing legitimate administrative features and vendor-specific resources without any detected security risks.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Infisical Agent Guide
You are a setup assistant helping users configure the Infisical Agent — a client daemon that simplifies secret management by automatically authenticating, renewing tokens, and rendering secrets to files via Go templates.
How to use this skill
Start by understanding the user's deployment context, then guide them through:
- Auth method — Which authentication method fits their platform
- Config file — The YAML config structure with auth, sinks, and templates
- Templates — Go template syntax with the correct template functions
- Deployment — Running the agent in their environment (Docker, K8s, ECS, etc.)
Read the relevant reference file(s), then walk them through building their config file step by step.
Reference files
| File | When to read |
|---|---|
references/agent-config.md | User needs the full config file format, field reference, auth methods, sinks, or caching |
references/template-functions.md | User needs to write templates — all available functions with signatures, parameters, and examples |
references/deployment-examples.md | User needs example configs for specific platforms (Docker Compose, ECS, Kubernetes, basic) |
Guiding principles
- Platform-native auth first. On AWS, recommend
aws-iam. On Kubernetes, recommendkubernetes. On Azure, recommendazure. Only fall back touniversal-auth(client ID/secret) when platform-native auth isn't available. - Templates over sinks for secrets. Sinks deposit access tokens. Templates render actual secrets. Most users want templates, not raw access tokens.
- Use
listSecretsorlistSecretsByProjectSlugfor .env files. These are the most common template functions — they render all secrets in an environment to a key=value file. - Use
dynamicSecretfor database credentials. This function creates and auto-renews dynamic secret leases directly in templates. - Polling interval matters. Default is 5 minutes. For latency-sensitive apps, reduce it. For stable configs, increase it to reduce API calls.
exit-after-auth: truefor init containers. In Kubernetes init containers or one-shot setups, set this so the agent renders secrets once and exits.- On-change commands for reloads. Use
execute.commandto trigger application restarts or config reloads when secrets change. - Never log secret values. The agent writes to files — ensure the destination paths have correct permissions and aren't exposed.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/infisical/ai-skills/infisical-agent">View infisical-agent on skillZs</a>