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/RD-DCS/venutian-antfarmWrote 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/rd-dcs/venutian-antfarm/infrastructure-ops)<a href="https://agentmods.dev/agents/rd-dcs/venutian-antfarm/infrastructure-ops"><img src="https://agentmods.dev/badge/agents/rd-dcs/venutian-antfarm/infrastructure-ops.svg" alt="Measured on agentmods" 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.00024 | $0.00472 |
| Opus 5 | $0.00012 | $0.00236 |
| Sonnet 5 | $0.00005 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
infrastructure-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 8d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 8d ago First seen · 53 lines · 24 tokens per session scan A 45911c5566cf
infrastructure-ops is an agent published in the GitHub repository RD-DCS/venutian-antfarm (5 stars, last pushed 5mo ago), with no licence file. It adds 24 tokens to every session and 472 once invoked, about $0.0001 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-31.
Other agents, from other repositories
kubernetes-expert
Kubernetes manifests, Helm charts, RBAC, HPA, network policies, and cluster troubleshooting specialist.
ops-proxmox
Proxmox VE infrastructure management (VMs, LXC, storage, network, backup).
factory-infra-scout
Read-only investigator for deployed infrastructure — Dokploy stacks, servers, containers, databases, DNS, health endpoints. Spawn it whenever a question needs SSH or container output to answer ("is the dev stack healthy?", "what is env var X on the deployed app?", "did the deploy pick up the new image?", "why is smoke…
ssh-admin
Linux server admin: SSH, Docker, systemd, Nginx, SSL. Triggers: ssh admin, server management.
hpc-platform-architect
Expert in designing centralized High-Performance Computing (HPC) platforms for modern vehicles. Specializes in hypervisor selection, AUTOSAR Adaptive integration, resource allocation, safety partitioning, and migration strategies from distributed ECU architectures to centralized compute.
k8s-locator
Locates Kubernetes resources matching criteria. Lists pods, deployments, services, and other K8s resources. Returns structured results without analyzing state. Use when you need to find resources broadly.