What is lima-ops CLAUDE.md?

A project guide for an Ansible system that creates and configures clusters inside Lima virtual machines. It supports Kubernetes clusters for running containerized services and MinIO clusters for object storage.

Use it when provisioning Lima disks and machines, generating inventories, preparing storage and networking, or deploying Kubernetes or MinIO.

It explains the project's three stages—creating the virtual machines, configuring them, and deploying applications—so changes are made in the right place.

How pavelanni/lima-ops configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to pavelanni/lima-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/pavelanni/lima-ops/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/pavelanni/lima-ops

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/pavelanni/lima-ops/claude-md/github.svg)](https://agentmods.dev/instructions/pavelanni/lima-ops/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/pavelanni/lima-ops/claude-md"><img src="https://agentmods.dev/badge/instructions/pavelanni/lima-ops/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/pavelanni/lima-ops/claude-md"><img src="https://agentmods.dev/badge/instructions/pavelanni/lima-ops/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,944 This file is loaded in full into every session.

When invoked 2,944 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02944	$0.02944
Opus 5.5	$0.01178	$0.01178
Sonnet 5.5	$0.00589	$0.00589
Haiku 4.5	$0.00294	$0.00294

Measured 2mo ago against content hash b04f52de252b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lima-ops CLAUDE.md 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 2mo 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.

CLAUDE.md · 342 lines

How it starts

The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

This is an Ansible-based project for provisioning and configuring clusters using Lima VMs. The project supports two deployment types:

Kubernetes-based clusters - For container orchestration and microservices
Bare-metal MinIO clusters - For high-performance object storage

The project separates infrastructure provisioning (VMs, disks, networking) from application deployment, allowing you to choose your deployment type after creating the infrastructure.

Architecture

The project follows a three-phase approach:

Infrastructure Provisioning Phase (runs on localhost):
- Creates Lima disks with flexible naming
- Creates Lima VM configuration files from Jinja2 templates
- Starts Lima VMs with specified resources (CPU, memory, disk)
- Generates inventory files for the cluster
VM Configuration Phase (runs on Lima VMs):
- Configures disk partitioning, formatting, and mounting
- Installs common packages and tools
- Prepares VMs for application deployment
Application Deployment Phase (runs on Lima VMs):
- Kubernetes path: Installs K8s components, initializes cluster
- Bare-metal MinIO path: Installs MinIO, configures distributed storage

Key Files Structure

Configuration Files:

vars/cluster_config.yml - Kubernetes cluster configuration
vars/baremetal_config.yml - Bare-metal MinIO cluster configuration

Infrastructure Playbooks:

provision_vms.yml - Creates Lima VMs and generates inventory
configure_vms.yml - Configures VMs with disk management
manage_disks.yml - Creates and manages Lima disks

Application Deployment:

deploy_baremetal_minio.yml - Installs bare-metal MinIO cluster
deploy_kubernetes_minio.yml - Installs Kubernetes cluster with AIStor (Commercial MinIO)
install_k3s.yml - K3s Kubernetes installation
install_k8s_prerequisites.yml - cert-manager, ingress-nginx, krew
install_directpv.yml - DirectPV storage provisioning
install_minio_operator.yml - AIStor Operator and Object Store (Helm-based)
configure_minio_ingress.yml - Ingress configuration for AIStor
verify_k8s_minio.yml - Installation verification

Read the full file on GitHub · 342 lines

Changes

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.

2mo ago First seen · 342 lines · 2,944 tokens per session scan A b04f52de252b

Subscribe to this mod's changes

lima-ops CLAUDE.md is an instructions file published in the GitHub repository pavelanni/lima-ops (6 stars, last pushed 11mo ago), licensed MIT. It adds 2,944 tokens to every session, about $0.0118 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-08-31.

lima-ops CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lima-ops CLAUDE.mdpavelanni/lima-ops	Instructions file	6	11mo ago	MIT	A	2,944	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

lima-ops: Instructions file for Claude Code