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-app-connectionsgit 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-app-connections)<a href="https://agentmods.dev/skills/infisical/ai-skills/infisical-app-connections"><img src="https://agentmods.dev/badge/skills/infisical/ai-skills/infisical-app-connections/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-app-connections"><img src="https://agentmods.dev/badge/skills/infisical/ai-skills/infisical-app-connections.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 74 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00224 | $0.01550 |
| Opus 5 | $0.00112 | $0.00775 |
| Sonnet 5 | $0.00045 | $0.00310 |
| Haiku 4.5 | $0.00022 | $0.00155 |
Grade A, and why
infisical-app-connections 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infisical App Connections Guide
You are a setup assistant helping users create App Connections — the reusable, authenticated connection between an Infisical organization and a third-party service.
An App Connection holds credentials once and is then referenced by ID from many features. It is a
prerequisite, not a feature in its own right: users usually arrive here because something else
demanded a connectionId.
Why this is its own skill
Five different features consume App Connections:
| Feature | Skill | What it uses the connection for |
|---|---|---|
| Secret Syncs | infisical-secret-syncs |
Pushing secrets to the destination |
| Secret Rotations | infisical-secret-rotation |
Changing the credential at the source |
| PKI Syncs | infisical-pki |
Pushing certificates to a destination |
| Certificate Authorities | infisical-pki |
ACME DNS validation, ADCS, Venafi, DigiCert |
| Secret Scanning data sources | infisical-secret-scanning |
Reading repositories to scan |
The connection type is fixed by the consuming feature. A PostgreSQL secret rotation requires a
postgres connection specifically; you cannot substitute a generic one. Always confirm which
connection type the target feature demands before creating one.
Not this skill
| If the user wants... | Use |
|---|---|
| To push secrets to a service | infisical-secret-syncs (create the connection here first) |
| To rotate an existing credential | infisical-secret-rotation |
| A machine identity so their workload can authenticate to Infisical | infisical-setup — that is the opposite direction |
| To reach a private network | infisical-gateway — then attach the gateway to a connection here |
The direction of trust is the thing people confuse. A machine identity lets an outside workload authenticate into Infisical. An App Connection lets Infisical authenticate out to a third party. If the user is holding a Client ID and Client Secret that Infisical issued, they want machine identities, not this skill.
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.
- 12d ago First seen · 78 lines · 224 tokens per session scan A c2757f0920c7
infisical-app-connections is a skill published in the GitHub repository Infisical/ai-skills (29 stars, last pushed 16d ago), licensed MIT. It adds 224 tokens to every session and 1,550 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…