Radar is a single-binary graphical interface for Kubernetes, the system used to run and manage containerized applications across clusters. It helps developers and operators inspect resources, topology, events, Helm deployments, GitOps, traffic, audits, and upgrade impact, while its built-in MCP server lets AI agents inspect and operate clusters through Radar.
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 skills/skyhook-io/radar/test-radarnpx skills add skyhook-io/radar --skill test-radargit 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/skills/skyhook-io/radar/test-radar)<a href="https://agentmods.dev/skills/skyhook-io/radar/test-radar"><img src="https://agentmods.dev/badge/skills/skyhook-io/radar/test-radar.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.00021 | $0.00060 |
| Opus 5 | $0.00010 | $0.00030 |
| Sonnet 5 | $0.00004 | $0.00012 |
| Haiku 4.5 | $0.00002 | $0.00006 |
Grade A, and why
test-radar 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.
What it actually says
Follow the workflow in .claude/commands/test-radar.md.
Do not modify the Claude command file. Treat it as the canonical workflow source for this repository.
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 · 9 lines · 21 tokens per session scan A 95bdce724ba8
test-radar is a skill published in the GitHub repository skyhook-io/radar (3,254 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 60 once invoked, about $0.0001 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 skills, from other repositories
k8s-deployer
Kubernetes deployment management - generate manifests, Helm charts, manage rollouts, check cluster status, and apply security best practices.
refactor
Refactors code following Ousterhout's design principles. Analyzes complexity, creates prioritized refactoring plan, and executes with safety-first approach. Optimized for Vite/React, Tauri/Rust, Zustand stack.
software-design-review
Analyzes code based on John Ousterhout's "A Philosophy of Software Design". Identifies unnecessary complexity, shallow modules, information leaks, and design problems. Use when reviewing architecture, PRs, refactoring, or asking about code quality.
vet
Run vet immediately after ANY logical unit of code changes. Do not batch your changes, do not wait to be asked to run vet, make sure you are proactive.
release-chart
Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump Chart.yaml/artifacthub-pkg.yml/values.yaml, regenerate docs, tag the release so CI publishes it). Trigger on requests like "release…
argocd-expert
Expert-level ArgoCD GitOps deployment, application management, sync strategies, and production operations.