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.
Borrowing it
Nothing to install: this file belongs to skyhook-io/radar. 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/skyhook-io/radar/main/.agents/skills/whats-new/SKILL.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/skills/skyhook-io/radar/whats-new)<a href="https://agentmods.dev/skills/skyhook-io/radar/whats-new"><img src="https://agentmods.dev/badge/skills/skyhook-io/radar/whats-new/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.
<a href="https://agentmods.dev/skills/skyhook-io/radar/whats-new"><img src="https://agentmods.dev/badge/skills/skyhook-io/radar/whats-new.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.01905 |
| Opus 5.5 | $0.00020 | $0.00762 |
| Sonnet 5.5 | $0.00010 | $0.00381 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
whats-new 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Radar What's New
Turn the release's actual work into useful, accurate highlights. Start with the whole release range, group related changes by user benefit, and use the existing scoring and acknowledgement model. Paths below are relative to the repo root.
Ask about companion work
Unless the request or earlier instructions already answer these, ask together:
- Should this also check for missing or outdated documentation in Radar OSS,
radar-docs, or both? - Should this also check the Radar changelog in
marketing, and is the scope audit-only or preparing/updating entries?
Honor explicit inclusions and skips; do not ask again when already instructed. Continue the core What's New work while awaiting answers, but do not start the optional work without an answer. Report unanswered companion scope as pending, not as approved or silently completed.
When either is included, read companion-repos.md for sibling discovery, clean-main/GPRA versus isolated-worktree handling, docs ownership, the marketing changelog skill, and mandatory worktree cleanup.
Read the contract
web/src/components/whats-new/releaseNotes.ts: catalog, importance scale, composition, weights, card/line limits, and auto-open threshold.web/src/components/whats-new/WhatsNew.tsx: Home-only announcement, acknowledgement, preview parameters, and local/shared/cloud behavior.WhatsNew.test.tsandWhatsNewDialog.test.tsxin that directory: pure composition and rendered-dialog regression coverage.scripts/check-whats-new.sh: release-entry gate. A passing gate proves that an entry exists, not that its copy is accurate or that it auto-opens.DESIGN.mdfor UI changes. Readinternal/server/whats_new.goand the API hooks inweb/src/api/client.tsif changing storage or acknowledgement.
Gather and group before choosing cards
- Establish the target version/ref and previous minor-release tag. Include all
merged work since that tag, including patches already merged for the target
minor. Refresh remote history when the task asks what has merged recently.
Use
git log --reverse --format='%h %s' <previous-minor-tag>..<target-ref>as an inventory, then inspect the actual diffs, producer code, and area docs. A commit count is not a PR count, and a commit subject is not proof of a claim. - Build candidate buckets around coherent user benefits, not one card per PR. Several related fixes can make a substantial improvement together. For example, reading-position stability, selection without auto-scroll, and container-start waiting belong in Log viewer improvements.
- Compare candidates against the existing cards and previous releases before deciding that nothing else makes the cut. Keep separate outcomes separate; do not split one improvement across cards just to count it twice.
- Show the proposed titles, included work, evidence, importance, and resulting composition. Surface real editorial choices before changing the release story. For a narrow wording edit, keep the scope narrow.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 164 lines · 50 tokens per session scan A d3904808124b
whats-new is a skill published in the GitHub repository skyhook-io/radar (3,969 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 1,905 once invoked, about $0.0002 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-10-25.
Other skills, from other repositories
cloud-native-gitops-workflows
Use this skill when the user says 'gitops workflow', 'environment promotion', 'app of apps', 'applicationset', 'multi-cluster gitops', 'secrets in gitops', 'sealed secrets', 'external secrets operator', 'gitops repo structure', 'flux vs argocd'. Designs the GitOps operating model: repository layout, environment…
cloud-native-argocd-reconciliation
Use this skill when the user says 'argocd reconciliation', 'argocd drift detection', 'why is my app OutOfSync', 'argocd diff', 'ignoreDifferences', 'server-side diff', 'argocd sync waves', 'argocd refresh vs sync', 'argocd application controller internals'. Explains how Argo CD's repo-server, application controller…
argocd
Operate Argo CD GitOps with AppProjects, safe automated sync/prune, and RespectIgnoreDifferences—debug OutOfSync/Degraded without kubectl drift that fights the controller.
k8s-deployer
Kubernetes deployment management - generate manifests, Helm charts, manage rollouts, check cluster status, and apply security best practices.
kubernetes-expert
Expert-level Kubernetes cluster management, deployment strategies, networking, and production operations. Use when the user mentions containers, orchestration, devops, or cloud native, or when the task involves Kubernetes Architecture, Pods, Deployments, or Services.
argocd-expert
Expert-level ArgoCD GitOps deployment, application management, sync strategies, and production operations. Use when the user mentions GitOps, Kubernetes, continuous deployment, declarative, or automation, or when the task involves ArgoCD Architecture, Application CRD, AppProject, or ApplicationSet.