Borrowing it
Nothing to install: this file belongs to atilladeniz/Kubeli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/atilladeniz/Kubeli/main/CLAUDE.mdgit clone --depth 1 https://github.com/atilladeniz/KubeliWrote 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/atilladeniz/kubeli/claude-md)<a href="https://agentmods.dev/instructions/atilladeniz/kubeli/claude-md"><img src="https://agentmods.dev/badge/instructions/atilladeniz/kubeli/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.1 | $0.02071 | $0.02071 |
| Opus 5 | $0.01035 | $0.01035 |
| Sonnet 5 | $0.00414 | $0.00414 |
| Haiku 4.5 | $0.00207 | $0.00207 |
Grade A, and why
Kubeli 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 9d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubeli - Kubernetes Management Desktop App
Project Overview
Kubeli is a modern Kubernetes management desktop application built with:
- Frontend: Vite + React 19
- Desktop: Tauri 2.9 (Rust backend)
- State: Zustand
- Styling: Tailwind CSS
- K8s Client: kube-rs (Rust)
Quick Start
# Development (Tauri + Vite)
make dev
# Web only development
make web-dev
# Production build
make build
Development Commands
Using Make (Recommended)
| Command | Description |
|---|---|
make dev |
Start Tauri development environment |
make web-dev |
Start Vite only (no Tauri) |
make build |
Build production Tauri app (macOS) |
make build-windows |
Cross-compile Windows NSIS installer from macOS |
make build-all |
Build macOS and Windows installers (Linux built by CI) |
make lint |
Run ESLint |
make format |
Format code with Prettier |
make check |
Run TypeScript type checking |
make rust-check |
Check Rust code |
make rust-fmt |
Format Rust code |
make clean |
Clean build artifacts |
make install |
Install all dependencies (incl. vet if Python available) |
make vet |
AI code review of all branch changes against main |
make vet-install |
Install vet CLI for AI code verification |
make help |
Show all available commands |
Release & Deploy
| Command | Description |
|---|---|
make release |
Release via CI: version bump, AI-generated changelog, commit, tag push → CI builds all platforms |
make release-push |
Review and publish a prepared release after explicit terminal confirmation |
make release-ai-dry-run |
Test Claude, Codex, and OpenCode release integration without changing release files |
make release-changelog-dry-run |
Test the real Claude → Codex → OpenCode fallback chain without changing release files |
make release-manual-dry-run |
Test the Markdown prompt and terminal paste fallback without changing release files |
make build-deploy |
Alias for make release |
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.
- 9d ago First seen · 241 lines · 2,071 tokens per session scan A 8adb48180746
Kubeli CLAUDE.md is an instructions file published in the GitHub repository atilladeniz/Kubeli (378 stars, last pushed yesterday), licensed MIT. It adds 2,071 tokens to every session, about $0.0104 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-30.
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).
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).
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.
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.