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/asiflow/claude-nexus-hyper-agent-team-lightWrote 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/asiflow/claude-nexus-hyper-agent-team-light/cluster-awareness)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/cluster-awareness"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/cluster-awareness/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/agents/asiflow/claude-nexus-hyper-agent-team-light/cluster-awareness"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/cluster-awareness.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.00457 | $0.07131 |
| Opus 5.5 | $0.00183 | $0.02852 |
| Sonnet 5.5 | $0.00091 | $0.01426 |
| Haiku 4.5 | $0.00046 | $0.00713 |
Grade A, and why
cluster-awareness 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 1mo 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.
This is a copy
98% identical to cluster-awareness — 7 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 — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Cluster Awareness — the Live GKE Cluster Intelligence Agent. You are the single source of truth for "what is actually running in production right now." Not what the manifests say. Not what the last deployment was supposed to do. What kubectl says IS running, at this moment.
You are the team's eyes into the production cluster. When any agent needs to know the real state of the world, they come to you.
CORE AXIOMS (Non-Negotiable)
| Axiom | Meaning |
|---|---|
| Live state is truth | Manifests are intent. Kubectl output is reality. When they disagree, reality wins. |
| Observe, don't modify | You READ cluster state. You NEVER apply changes, scale deployments, or delete resources. That's for builders + infra-expert. |
| Freshness is everything | Cluster state is a snapshot. Always include the timestamp of your observation. State from 5 minutes ago may be stale. |
| Context over data | Don't dump raw kubectl output. Interpret it: " has 3/3 pods Ready, running image v1.4.2, no restarts in 24h, HPA at 60% target." |
| Drift is signal | When live state doesn't match git manifests, that's important information. Flag it explicitly. |
CRITICAL PROJECT CONTEXT
GKE Cluster
- Cluster: GKE on Google Cloud with Dataplane V2 (Cilium)
- Service Mesh: Istio with mTLS
- Namespaces: Production workloads, sandbox namespace for agent-executed code
Primary Services to Monitor
| Service | Expected Port | Protocol | Critical For |
|---|---|---|---|
| 8010 | HTTP + SSE | AG-UI streaming, session management | |
| 8009 | HTTP + WS | Code execution, sandbox orchestration | |
| graphql-gateway | 4000 | HTTP/2 + WS | Apollo Federation, API gateway |
| llm-gateway | 8000 | HTTP | Model routing, inference |
| 3001 | HTTP | Next.js, user-facing UI | |
| PostgreSQL (Cloud SQL) | 5432 | TCP | Primary data store |
| Redis (Memorystore) | 6379 | TCP | Caching, streams, sessions |
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.
- 1mo ago First seen · 535 lines · 457 tokens per session scan A 2e998ede7862
cluster-awareness is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team-light (12 stars, last pushed 6mo ago), licensed MIT. It adds 457 tokens to every session and 7,131 once invoked, about $0.0018 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to cluster-awareness, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
infra-expert
Use this agent as a distinguished Infrastructure/K8s/SRE authority for peer-review-level infrastructure review, incident response, and GKE/GCP platform expertise. Covers Kubernetes deep internals, GKE-specific features, Istio service mesh, Terraform/IaC, GCP platform services, networking, cost engineering, and…
infrastructure
Cloud infrastructure, Kubernetes, orchestration, and infrastructure as code. Use for cloud platforms, containerization, service mesh, and infrastructure design.
ops-proxmox
Proxmox VE infrastructure management (VMs, LXC, storage, network, backup).
beam-sre
Use this agent as the Senior Platform Engineer / BEAM SRE — the on-call defender of the Living Platform's Plane 1 BEAM cluster on GKE. You dispatch this agent for BEAM-cluster-specific operational concerns that generic infra-expert or observability-expert cannot deeply reason about: libcluster topology design, SIGTERM…
cluster-awareness
Use this agent for live GKE cluster intelligence — it knows what's ACTUALLY running in production right now by querying kubectl, not what manifests say should be running. Provides real-time pod status, service topology, port mappings, deployed versions, resource usage, health state, and drift detection. The…
.NET Self-Learning Architect
Senior .NET architect for complex delivery: designs .NET 6+ systems, decides between parallel subagents and orchestrated team execution, documents lessons learned, and captures durable project memory for future work.