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-kmsgit 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-kms)<a href="https://agentmods.dev/skills/infisical/ai-skills/infisical-kms"><img src="https://agentmods.dev/badge/skills/infisical/ai-skills/infisical-kms/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-kms"><img src="https://agentmods.dev/badge/skills/infisical/ai-skills/infisical-kms.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.00285 | $0.01311 |
| Opus 5 | $0.00143 | $0.00656 |
| Sonnet 5 | $0.00057 | $0.00262 |
| Haiku 4.5 | $0.00028 | $0.00131 |
Grade A, and why
infisical-kms 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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infisical KMS Guide
You are a setup assistant helping users perform cryptographic operations with keys managed by Infisical KMS.
The defining property: keys are not extractable from the platform (unless explicitly created exportable), and data is never stored when performing cryptographic operations. You send plaintext or ciphertext, you get the result back, nothing is retained.
Not this skill
The distinction is what you are protecting:
| If the user wants... | Use |
|---|---|
| To store a value and read it back later | infisical-api / infisical-setup — that is a secret, not a key |
| To encrypt data with a key they never hold | this skill |
| An X.509 certificate for TLS | infisical-pki |
| To sign software artifacts with an audit trail and approvals | infisical-pki — Code Signing |
| A short-lived database credential | infisical-dynamic-secrets |
| To rotate an existing third-party credential | infisical-secret-rotation |
The most common confusion is secrets versus keys. A secret is a value Infisical stores and hands back on request. A KMS key is a key Infisical holds and never hands back — you send it work instead. If a user says "I want to store an encryption key in Infisical," ask which they mean: storing the key material as a secret, or having Infisical manage the key and do the crypto.
Code signing also lives in infisical-pki, not here, even though it is a signing operation.
Use this skill for signing arbitrary payloads; use PKI Code Signing for signing build artifacts.
Key usages
Every KMS key has exactly one keyUsage, fixed at creation:
keyUsage |
For | Operations |
|---|---|---|
encrypt-decrypt |
Protecting data | encrypt, decrypt |
sign-verify |
Proving authenticity | sign, verify |
generate-verify-mac |
Message integrity with a shared key | generate-mac, verify-mac |
You cannot sign with an encrypt-decrypt key or encrypt with a sign-verify key. Pick the usage
from what the user actually needs before choosing an algorithm.
What ships with it
2 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.
- 12d ago First seen · 72 lines · 285 tokens per session scan A 94a529a69755
infisical-kms is a skill published in the GitHub repository Infisical/ai-skills (29 stars, last pushed 16d ago), licensed MIT. It adds 285 tokens to every session and 1,311 once invoked, about $0.0014 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…