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/skyhook-io/radar/claude-mdgit clone --depth 1 https://github.com/skyhook-io/radarWrote 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/skyhook-io/radar/claude-md)<a href="https://agentmods.dev/instructions/skyhook-io/radar/claude-md"><img src="https://agentmods.dev/badge/instructions/skyhook-io/radar/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.09186 | $0.09186 |
| Opus 5 | $0.04593 | $0.04593 |
| Sonnet 5 | $0.01837 | $0.01837 |
| Haiku 4.5 | $0.00919 | $0.00919 |
Grade C, and why
radar CLAUDE.md scanned grade C 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 yesterday.
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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
│ (~/.kube/config) │ How it starts
The opening of the file, as written. The whole thing — 299 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 this repository.
Project Overview
Radar is a modern Kubernetes visibility tool — local-first, no account required, no cloud dependency, fast. It provides topology visualization, event timeline, service traffic maps, resource browsing, Helm management, cluster audit (best-practices scanning), and Kubernetes upgrade impact analysis. Runs as a kubectl plugin (kubectl-radar) or standalone binary and opens a web UI in the browser. Open source, free forever. Built by Skyhook.
Code comments
- Default to writing no comments. Only add one when the WHY is non-obvious — a hidden constraint, a subtle invariant, a workaround for a specific bug, or behavior that would surprise a reader.
- Don't explain WHAT the code does — well-named identifiers already do that.
- Don't reference tickets, PRs, bug numbers, or diff history in code comments (e.g. "fixes SKY-123", "Bugbot caught this on PR #584", "used to read X, now…"). Those belong in the PR description and rot as the codebase evolves. The WHY of the change should stand on its own.
- This applies to comments written by any tool (Cursor, Bugbot, Copilot) as well as humans — strip ticket/PR references before merging.
Release and publishing authorization
- Never create, move, or delete Git tags or GitHub Releases; dispatch release or publish workflows; or publish binaries, container images, npm packages, package-manager artifacts, Helm charts, or other distribution artifacts without explicit user approval naming the exact artifact, version, and action.
- Approval to implement a change, open or merge a PR, or prepare release changes is not authorization to publish. If release authorization is ambiguous, stop and ask.
Reference Docs — MUST READ before making changes
Not everything is in this file. The following files contain critical details that are not duplicated here. You MUST read them when working in the relevant area — do not guess or rely on memory.
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.
- yesterday Changed · +1 lines · +53 tokens per session 05f5f5baf094
- 4d ago First seen · 298 lines · 9,133 tokens per session scan C 9ab04b1d3a01
radar CLAUDE.md is an instructions file published in the GitHub repository skyhook-io/radar (3,232 stars, last pushed today), licensed Apache-2.0. It adds 9,186 tokens to every session, about $0.0459 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
Kubeli CLAUDE.md
Instructions for atilladeniz/Kubeli, covering kubeli - kubernetes management desktop app, project overview, quick start, development (tauri + vite) and web only development.
Kubeli AGENTS.md
Instructions for atilladeniz/Kubeli: For project-specific conventions, commands, architecture, and workflow, consult CLAUDE.md first.
charts CLAUDE.md
Instructions for duyet/charts, covering claude.md - project philosophy & development guide, the vision, core principles, 1. simplicity without losing power and 2. consistency is kindness.
helm-zabbix CLAUDE.md
Instructions for zabbix-community/helm-zabbix, covering claude.md, repository overview, common commands, architecture and template/value organization.
klustr AGENTS.md
Instructions for SametKUM/klustr, covering klustr, tech stack, project structure, architecture patterns and live data flow — informer pattern.
home-ops AGENTS.md
Instructions for edgard/home-ops, covering home ops, build & test, developer loop, project layout and conventions.