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.
git clone --depth 1 https://github.com/smicolon/ai-kitWrote 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/commands/smicolon/ai-kit/infisical-ci-setup)<a href="https://agentmods.dev/commands/smicolon/ai-kit/infisical-ci-setup"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/infisical-ci-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/commands/smicolon/ai-kit/infisical-ci-setup"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/infisical-ci-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00018 | $0.01863 |
| Opus 5 | $0.00009 | $0.00932 |
| Sonnet 5 | $0.00004 | $0.00373 |
| Haiku 4.5 | $0.00002 | $0.00186 |
Grade B, and why
infisical-ci-setup scanned grade B with 3 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 6d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
curl -1sLf 'https://dl.cloudsmith.io/public/infisical/infisical-cli/setup.deb.sh' | sudo -E bash Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- curl -1sLf 'https://dl.cloudsmith.io/public/infisical/infisical-cli/setup.deb.sh' | bash Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -1sLf 'https://dl.cloudsmith.io/public/infisical/infisical-cli/setup.deb.sh' | sudo -E bash How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infisical CI Setup Command
Generate CI/CD pipeline configuration for injecting Infisical secrets into builds and deployments.
Parse Arguments
Extract from user input:
- provider:
github,gitlab,circleci,jenkins, orbitbucket
Workflow
Step 1: Determine CI Provider
Ask user which CI/CD provider they use:
- GitHub Actions
- GitLab CI
- CircleCI
- Jenkins
- Bitbucket Pipelines
Step 2: Create Machine Identity
Guide user through Infisical dashboard:
- Go to Organization Settings > Machine Identities
- Click Create Identity
- Name:
ci-<provider>-<project>(e.g.,ci-github-myapp) - Add Universal Auth method
- Copy Client ID and Client Secret
- Add identity to the project with access to required environments
Step 3: Store Credentials in CI
Guide user to add these secrets to their CI provider:
| Secret Name | Value |
|---|---|
INFISICAL_UNIVERSAL_AUTH_CLIENT_ID |
Client ID from step 2 |
INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET |
Client Secret from step 2 |
For self-hosted, also add:
| INFISICAL_API_URL | https://secrets.company.com/api |
Step 4: Generate Pipeline Config
GitHub Actions
Create .github/workflows/deploy.yml (or add to existing):
name: Deploy
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Install Infisical CLI
run: |
curl -1sLf 'https://dl.cloudsmith.io/public/infisical/infisical-cli/setup.deb.sh' | sudo -E bash
sudo apt-get update && sudo apt-get install -y infisical
- name: Authenticate with Infisical
run: |
infisical login --method=universal-auth \
--client-id=${{ secrets.INFISICAL_UNIVERSAL_AUTH_CLIENT_ID }} \
--client-secret=${{ secrets.INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET }}
env:
INFISICAL_DISABLE_UPDATE_CHECK: "true"
- name: Build with secrets
run: infisical run --env=production -- npm run build
- name: Deploy
run: infisical run --env=production -- npm run deploy
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.
- 6d ago First seen · 270 lines · 18 tokens per session scan B a51224d416cf
infisical-ci-setup is a command published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 1,863 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
pr-quality-gate-devops
You are reviewing a pull request for CI/CD, build, deployment, and infrastructure concerns.
pr-quality-gate-architect
You are reviewing a pull request for architectural design and system structure concerns.
pr-quality-gate-decision-rigor
You are reviewing a pull request for the quality of the reasoning behind a decision, not just the code that implements it.
pr-quality-gate-agent-safety
You are reviewing a pull request for agent-safety risk: changes that alter how an autonomous agent behaves, what it can run, or what guardrails it must clear before acting.
pr-quality-gate-analyst
You are reviewing a pull request for code quality, impact, and maintainability.
pr-quality-gate-code-quality
You are reviewing a pull request for the maintainability of the code it changes: how cohesive, loosely coupled, encapsulated, testable, and non-redundant the touched code is, and whether the author left each file at least as clean as they found it.