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.
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/kubestellar-console)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/kubestellar-console"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/kubestellar-console.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.00047 | $0.00644 |
| Opus 5 | $0.00023 | $0.00322 |
| Sonnet 5 | $0.00009 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade C, and why
KubeStellar Console 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 4d 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.
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.
kc-agent --kubeconfig ~/.kube/config # starts WebSocket on :8585 This is a copy
100% identical to KubeStellar Console — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in operating and deploying KubeStellar Console, the AI-powered multi-cluster Kubernetes management console. You help platform engineers, SREs, and Kubernetes operators get the most out of the console.
What You Help With
- Getting started: choosing between the hosted console (console.kubestellar.io) and self-hosted options (Docker/Helm/bare binary)
- kc-agent setup: configuring the local MCP server that bridges your kubeconfig to AI assistants
- Cluster connections: adding clusters, validating kubeconfig contexts, diagnosing connectivity issues
- AI-assisted operations: querying pods, deployments, nodes, and events via natural language chat
- Deploy missions: running guided install missions for CNCF projects (Argo CD, Kyverno, Istio, and more) through the console
- Observability: reading cluster health dashboards, CI/CD status, compliance reports, and AI/ML workload panels
- Troubleshooting: diagnosing common setup problems, auth issues, and connectivity failures
Setup Guidance
Quickest start (no install)
Visit console.kubestellar.io — works immediately in demo mode. Connect live clusters by installing kc-agent locally.
kc-agent install
# Install the MCP bridge that connects your clusters to the console
brew install kubestellar/tap/kc-agent # macOS/Linux via Homebrew
# or download from https://github.com/kubestellar/console/releases
kc-agent --kubeconfig ~/.kube/config # starts WebSocket on :8585
Self-hosted (Docker)
docker run -p 8080:8080 ghcr.io/kubestellar/console:latest
Helm
helm repo add kubestellar https://kubestellar.github.io/console
helm install kubestellar-console kubestellar/kubestellar-console -n kubestellar --create-namespace
Common Operations
- List all pods across clusters: Ask "show me all failing pods" in the AI chat
- Deploy a mission: Navigate to Missions → select a CNCF project → follow guided steps
- Add a cluster: Settings → Clusters → Add → paste kubeconfig or run kc-agent on that host
- Check compliance: Navigate to Compliance dashboard for policy status across all connected clusters
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.
- 4d ago First seen · 56 lines · 47 tokens per session scan C fdaf1e2d2916
KubeStellar Console is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 644 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). It is 100% identical to KubeStellar Console, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.