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/.claude/commands/test-radar.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/commands/skyhook-io/radar/test-radar)<a href="https://agentmods.dev/commands/skyhook-io/radar/test-radar"><img src="https://agentmods.dev/badge/commands/skyhook-io/radar/test-radar/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/commands/skyhook-io/radar/test-radar"><img src="https://agentmods.dev/badge/commands/skyhook-io/radar/test-radar.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.00000 | $0.00730 |
| Opus 5.5 | $0.00000 | $0.00292 |
| Sonnet 5.5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
test-radar scanned grade A 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. **Start server**: Run the built binary with `--port <random-port> --no-open` in the background. Wait for it to be ready (curl the health endpoint or `/api/cluster-info`). How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Radar
Build and test Radar changes using a real running instance. Combines build verification, API smoke tests, and optional Playwright E2E tests.
Prerequisites
Playwright MCP: Check if the Playwright MCP tools are available (e.g., mcp__playwright__browser_navigate). If NOT available, tell the user "Playwright MCP is not available — please add it to your MCP config and restart" and stop. Do not attempt workarounds.
Setup
- Pick a random port (e.g., 9300-9399 range) for the backend to avoid conflicting with other running Radar instances.
- Build: Run
make buildfrom the repo root. If it fails, diagnose and report — do not proceed. - Start server: Run the built binary with
--port <random-port> --no-openin the background. Wait for it to be ready (curl the health endpoint or/api/cluster-info).
Test Plan
Create a test plan based on the current changes (check git diff main..HEAD --name-only to scope what changed). Then execute what you can autonomously.
What to test yourself:
- API smoke tests: Hit key API endpoints via curl/fetch and verify they return valid responses (200, correct JSON structure). Good candidates:
/api/cluster-info,/api/resource-counts,/api/resources/pods,/api/dashboard,/api/events/stream(SSE — connect briefly, verify event format). - Frontend loads: Use Playwright to navigate to
http://localhost:<port>, verify the page loads without console errors, key UI elements render. - Feature-specific tests: Based on the diff, test the specific feature that changed. For SSE-related changes, connect to the SSE stream and verify events arrive. For UI changes, use Playwright to verify rendering. For API changes, hit the relevant endpoints.
What to flag for manual testing:
- Anything requiring
kubectlcommands against a live cluster (you don't know if one is connected) - Destructive operations (creating/deleting K8s resources)
- Visual/UX verification that can't be checked programmatically
- Multi-browser or performance testing
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.
- 2mo ago First seen · 50 lines · 0 tokens per session scan A d69197cfdd0a
test-radar is a command published in the GitHub repository skyhook-io/radar (3,969 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 730 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
verify-pr
Verify a PR's frontend changes through browser automation.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
test-run
Run E2E tests with qa-use CLI.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.