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 selvarajmurugesan90/ops-engineering-skills --skill on-prem-infrastructure-patternsgit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-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/selvarajmurugesan90/ops-engineering-skills/on-prem-infrastructure-patterns)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/on-prem-infrastructure-patterns"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/on-prem-infrastructure-patterns/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/selvarajmurugesan90/ops-engineering-skills/on-prem-infrastructure-patterns"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/on-prem-infrastructure-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Tool Misuse · line 150 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Data Exfiltration · line 150 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00150 | $0.04151 |
| Opus 5.5 | $0.00060 | $0.01660 |
| Sonnet 5.5 | $0.00030 | $0.00830 |
| Haiku 4.5 | $0.00015 | $0.00415 |
Grade A, and why
on-prem-infrastructure-patterns scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -k -u "<BMC_USER>:<BMC_PASSWORD>" \ How it starts
The opening of the file, as written. The whole thing — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
On-Prem Infrastructure Patterns
Purpose
Not every workload belongs in the public cloud, and not every organization can (or should) migrate everything at once — data residency law, sub-millisecond latency requirements, existing capital investment in depreciating hardware, or genuinely predictable steady-state capacity all make on-premises or private-cloud infrastructure the correct choice for at least part of most large estates. But on-prem infrastructure without the same engineering discipline applied to cloud — inventory as code, IaC- driven provisioning, redundant hybrid connectivity, deliberate workload placement — degenerates into hand-built snowflake servers, spreadsheet inventories that drift from physical reality, and a single point of failure between the data center and everything the business has since moved to the cloud. This skill covers the common virtualization baseline (VMware vSphere), automated bare-metal provisioning, inventory-as-code discipline, and the hybrid connectivity patterns that let on-prem and cloud infrastructure operate as one coherent estate rather than two disconnected islands.
When to use
- Designing or expanding a private-cloud/data-center footprint: a new vSphere cluster, a bare-metal fleet, or a colocation build-out.
- Automating bare-metal server provisioning (OS install, firmware baseline, network configuration) instead of manual per-server setup.
- Planning or troubleshooting hybrid connectivity between an on-premises data center and a public cloud (VPN, dedicated circuit, DNS/IP integration).
- Deciding whether a specific workload should stay on-premises, burst to cloud, or migrate fully — using a documented framework rather than defaulting to "cloud, always."
- Building or auditing an infrastructure-as-code pipeline for on-prem resources (Terraform against vSphere/bare-metal providers, Ansible configuration baselines).
- Establishing or fixing an IPAM/DCIM inventory that has drifted from what's physically racked and cabled.
- Planning capacity ahead of a hardware refresh cycle, given that procurement lead times (weeks to months) are nothing like cloud elasticity.
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 · 358 lines · 150 tokens per session scan A 2ccf62893073
on-prem-infrastructure-patterns is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (42 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 150 tokens to every session and 4,151 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".