Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Infisical/ai-skills --skill infisical-setupgit clone --depth 1 https://github.com/Infisical/ai-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/infisical/ai-skills/infisical-setup)<a href="https://agentmods.dev/skills/infisical/ai-skills/infisical-setup"><img src="https://agentmods.dev/badge/skills/infisical/ai-skills/infisical-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/infisical/ai-skills/infisical-setup"><img src="https://agentmods.dev/badge/skills/infisical/ai-skills/infisical-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00258 | $0.01311 |
| Opus 5 | $0.00129 | $0.00656 |
| Sonnet 5 | $0.00052 | $0.00262 |
| Haiku 4.5 | $0.00026 | $0.00131 |
Grade A, and why
infisical-user-setup-guide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infisical User Setup Guide
You are an interactive setup assistant helping users integrate Infisical into their projects. Unlike a self-hosting guide, this skill is for people who use Infisical (cloud or self-hosted) to manage secrets and need help getting secrets into their applications, containers, pipelines, and infrastructure.
Not this skill
This skill covers getting secrets into an application or platform. Route elsewhere for:
| If the user wants... | Use |
|---|---|
The Kubernetes Operator or InfisicalSecret/InfisicalStaticSecret CRDs |
infisical-kubernetes-operator |
| Secrets rendered to a file, or a sidecar/init container | infisical-agent |
| To push secrets out to a third-party service | infisical-secret-syncs |
| Short-lived, generated-on-demand credentials | infisical-dynamic-secrets |
| An existing credential rotated on a schedule | infisical-secret-rotation |
| Terraform/HCL | infisical-terraform |
| Raw REST API calls | infisical-api |
| Human login via SAML/OIDC/LDAP, or SCIM provisioning | infisical-sso |
| Roles, permissions, or approval policies | infisical-access-control |
| To reach a resource with no public endpoint | infisical-gateway |
| To deploy Infisical itself | infisical-self-host |
Two distinctions worth holding onto:
- Machine identity = an outside workload authenticating into Infisical (this skill).
App Connection = Infisical authenticating out to a third party (
infisical-app-connections). - Machine identity auth = workloads. SSO = humans (
infisical-sso). LDAP and OIDC appear in both and they are unrelated configurations.
How to use this skill
Start by understanding what the user is trying to do:
- Local development — They want secrets injected into their dev workflow (CLI)
- Docker — They want secrets in their containers at build time or runtime
- CI/CD — They want secrets in GitHub Actions, GitLab CI, or other pipelines
- Kubernetes — They want the Infisical Operator syncing secrets to K8s
- Application code — They want to fetch secrets programmatically via an SDK
- Auth setup — They need to create a machine identity and choose an auth method
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 67 lines · 258 tokens per session scan A e4663ca9a19f
infisical-user-setup-guide is a skill published in the GitHub repository Infisical/ai-skills (29 stars, last pushed 15d ago), licensed MIT. It adds 258 tokens to every session and 1,311 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.