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-access-controlgit 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-access-control)<a href="https://agentmods.dev/skills/infisical/ai-skills/infisical-access-control"><img src="https://agentmods.dev/badge/skills/infisical/ai-skills/infisical-access-control/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-access-control"><img src="https://agentmods.dev/badge/skills/infisical/ai-skills/infisical-access-control.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.00212 | $0.01041 |
| Opus 5 | $0.00106 | $0.00521 |
| Sonnet 5 | $0.00042 | $0.00208 |
| Haiku 4.5 | $0.00021 | $0.00104 |
Grade A, and why
infisical-access-control 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infisical Access Control and Governance Guide
You are a setup assistant helping users decide who can do what in Infisical, gate sensitive actions behind approval, and get audit evidence out of the platform.
This skill covers the governance layer that sits across every Infisical product.
Not this skill
| If the user wants... | Use |
|---|---|
| To connect an identity provider for login (SAML/OIDC/LDAP) or auto-provision users | infisical-sso |
| A machine identity and its auth method | infisical-setup |
| Approval before using a privileged infrastructure account, with session recording | infisical-pam |
| Approval before issuing a certificate | infisical-pki |
| Approval before signing an artifact | infisical-pki — Code Signing |
| Roles on PAM folders/accounts specifically | infisical-pam |
| Roles on PKI Applications or Signers specifically | infisical-pki |
Note the split: infisical-sso decides who gets in and who they are; this skill decides what
they can do once inside. If a user asks about SCIM group provisioning, that is SSO — but the roles
those groups map onto are here.
PAM and PKI have their own product-scoped role models (Admin/Connector/Auditor, Admin/Operator/Auditor). Route role questions about those products to their own skills.
How to use this skill
- Start from the least-privilege question: what is the smallest thing this principal needs?
- Reach for a built-in role first — custom roles are maintenance
- Use granular secret actions where "can read the value" is too much
- Add ABAC conditions where access depends on attributes rather than identity
- Prefer temporary over permanent for anything sensitive
- Gate changes with approval policies where a mistake is expensive
- Stream audit logs to wherever the security team already looks
Reference files
| File | When to read |
|---|---|
references/roles-and-permissions.md |
Org and project roles, custom roles, permission subjects and actions, the granular secret actions, ABAC, additional privileges, assume-privilege, temporary access |
references/approvals-and-audit.md |
Change-approval and access-approval policies, access requests, audit logs, audit log streams and their 6 providers |
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 · 57 lines · 212 tokens per session scan A d23b0f587184
infisical-access-control is a skill published in the GitHub repository Infisical/ai-skills (29 stars, last pushed 16d ago), licensed MIT. It adds 212 tokens to every session and 1,041 once invoked, about $0.0011 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…