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 agentmods add instructions/pavelanni/lima-ops/claude-mdgit clone --depth 1 https://github.com/pavelanni/lima-opsWrote 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/instructions/pavelanni/lima-ops/claude-md)<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="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 | $0.02944 | $0.02944 |
| Opus 5 | $0.01472 | $0.01472 |
| Sonnet 5 | $0.00589 | $0.00589 |
| Haiku 4.5 | $0.00294 | $0.00294 |
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 5d 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 — 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 configurationvars/baremetal_config.yml- Bare-metal MinIO cluster configuration
Infrastructure Playbooks:
provision_vms.yml- Creates Lima VMs and generates inventoryconfigure_vms.yml- Configures VMs with disk managementmanage_disks.yml- Creates and manages Lima disks
Application Deployment:
deploy_baremetal_minio.yml- Installs bare-metal MinIO clusterdeploy_kubernetes_minio.yml- Installs Kubernetes cluster with AIStor (Commercial MinIO)install_k3s.yml- K3s Kubernetes installationinstall_k8s_prerequisites.yml- cert-manager, ingress-nginx, krewinstall_directpv.yml- DirectPV storage provisioninginstall_minio_operator.yml- AIStor Operator and Object Store (Helm-based)configure_minio_ingress.yml- Ingress configuration for AIStorverify_k8s_minio.yml- Installation verification
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.
- 5d ago First seen · 342 lines · 2,944 tokens per session scan A b04f52de252b
lima-ops CLAUDE.md is an instructions file published in the GitHub repository pavelanni/lima-ops (5 stars, last pushed 8mo ago), licensed MIT. It adds 2,944 tokens to every session, about $0.0147 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).