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 agents/kubestellar/console/k8s-debuggit clone --depth 1 https://github.com/kubestellar/consoleWhat 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.00029 | $0.01526 |
| Opus 5 | $0.00015 | $0.00763 |
| Sonnet 5 | $0.00006 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
k8s-debug 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 2d 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.
kubectl run -it --rm debug --image=curlimages/curl --restart=Never -- \ How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Debugging Agent
You help debug Kubernetes clusters and workloads that the KubeStellar Console manages or monitors.
Quick Debugging
# All pods across namespaces
kubectl get pods -A
# Failed/unhealthy pods
kubectl get pods -A --field-selector=status.phase!=Running,status.phase!=Succeeded
# Recent events
kubectl get events -A --sort-by='.lastTimestamp' | tail -30
# All deployments
kubectl get deployments -A
# Cluster info
kubectl cluster-info
Log Management
Always redirect large output to files to keep context clean:
export LOG_DIR=/tmp/console-k8s
mkdir -p $LOG_DIR
# Pattern: redirect output, check exit code
kubectl <command> > $LOG_DIR/<name>.log 2>&1 && echo "OK" || echo "FAIL (see $LOG_DIR/<name>.log)"
Pod Debugging
Check Pod Status
# Specific namespace
kubectl get pods -n <namespace>
# Describe a problem pod
kubectl describe pod <pod-name> -n <namespace>
# Check pod events
kubectl get events -n <namespace> --field-selector involvedObject.name=<pod-name>
View Pod Logs
# Current logs
kubectl logs -n <namespace> <pod-name> --tail=100
# Previous container (after crash)
kubectl logs -n <namespace> <pod-name> --previous
# Follow logs
kubectl logs -n <namespace> <pod-name> -f
# All pods in a deployment
kubectl logs -n <namespace> -l app=<label> --tail=50
Check Pod Environment
# Environment variables
kubectl get pod <pod-name> -n <namespace> -o jsonpath='{.spec.containers[0].env}' | jq
# Mounted volumes
kubectl exec -it <pod-name> -n <namespace> -- ls -la /etc/config/
# Resource limits
kubectl get pod <pod-name> -n <namespace> -o jsonpath='{.spec.containers[0].resources}'
Exec Into Pod
kubectl exec -it <pod-name> -n <namespace> -- /bin/sh
Service Debugging
Check Service Endpoints
kubectl get endpoints <service-name> -n <namespace>
kubectl get svc <service-name> -n <namespace> --show-labels
Port Forward
kubectl port-forward svc/<service-name> <local-port>:<service-port> -n <namespace>
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.
- 2d ago First seen · 232 lines · 29 tokens per session scan A 93f339ff1631
k8s-debug is an agent published in the GitHub repository kubestellar/console (130 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,526 once invoked, about $0.0001 per session on Opus 5. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.