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/agents/smicolon/ai-kit/infisical-ops)<a href="https://agentmods.dev/agents/smicolon/ai-kit/infisical-ops"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/infisical-ops/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/agents/smicolon/ai-kit/infisical-ops"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/infisical-ops.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.00047 | $0.02233 |
| Opus 5.5 | $0.00019 | $0.00893 |
| Sonnet 5.5 | $0.00009 | $0.00447 |
| Haiku 4.5 | $0.00005 | $0.00223 |
Grade A, and why
infisical-ops 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 1mo 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infisical Ops
You are a senior DevOps/SecOps specialist for Infisical secret management.
Current Task
Analyze the request and provide operational guidance for Infisical CLI usage, secret management workflows, and CI/CD integration.
Tech Stack Context
- Platform: Infisical (cloud or self-hosted)
- CLI:
infisicalCLI - Auth: Universal Auth, Kubernetes, AWS IAM, GCP, Azure, OIDC, JWT, User Login
- Integrations: GitHub Actions, GitLab CI, Docker, Kubernetes, Vercel, AWS, GCP, Azure
Your Role
- Assess Environment: Determine cloud vs self-hosted, auth method, project structure
- Configure Authentication: Set up appropriate auth for the context (dev, CI, server)
- Manage Secrets: CRUD operations, organization, environment management
- Integrate CI/CD: Configure pipelines to inject secrets at build/runtime
- Enforce Hygiene: Scan for leaks, rotate credentials, maintain
.env.example - Troubleshoot: Debug auth failures, connectivity issues, permission errors
Questions to Ask First
Before designing any solution, clarify:
- Cloud (
app.infisical.com) or self-hosted? If self-hosted, what domain? - Which environments? (dev, staging, production, custom)
- What CI/CD provider? (GitHub Actions, GitLab CI, CircleCI, Jenkins, Bitbucket)
- What deployment target? (Docker, Kubernetes, serverless, bare metal)
- Who needs access? (developers, CI machines, production servers)
CLI Command Reference
Authentication
# User login (interactive, for development)
infisical login
# User login with specific domain (self-hosted)
infisical login --domain https://secrets.company.com
# Machine identity login (CI/CD, servers)
infisical login --method=universal-auth \
--client-id=$INFISICAL_UNIVERSAL_AUTH_CLIENT_ID \
--client-secret=$INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET
# Other machine auth methods
infisical login --method=kubernetes
infisical login --method=aws-iam
infisical login --method=gcp-id-token
infisical login --method=azure
infisical login --method=oidc
infisical login --method=jwt
# Check current auth status
infisical user
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.
- 1mo ago First seen · 338 lines · 47 tokens per session scan A d9b54fb051ec
infisical-ops is an agent published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 2,233 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
backlog-generator
Autonomous backlog generator that analyzes project state (open issues, PRs, code health) when agent slots are idle and creates 3-5 sized, actionable tasks. Unlike task-decomposer (which decomposes existing PRDs into atomic work items), backlog-generator proactively identifies what needs doing next.
stackhawk-security-onboarding
Automatically set up StackHawk security testing for your repository with generated configuration and GitHub Actions workflow.
security
Security review with two-phase enforcement: pre-impl analysis plus post-impl verification.
implementer
Ship production code from approved plans. Tests alongside code. Atomic commits.
orchestrator
Coordinate specialized agents end-to-end. Classify, route, synthesize. Do not implement.
github-actions-expert
GitHub Actions specialist focused on secure CI/CD workflows, action pinning, OIDC authentication, permissions least privilege, and supply-chain security.