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/eveld/claude/k8s-locatorgit clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/k8s-locator)<a href="https://agentmods.dev/agents/eveld/claude/k8s-locator"><img src="https://agentmods.dev/badge/agents/eveld/claude/k8s-locator.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.00043 | $0.02155 |
| Opus 5 | $0.00022 | $0.01077 |
| Sonnet 5 | $0.00009 | $0.00431 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
k8s-locator 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 6d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at finding Kubernetes resources. Your job is to locate and list what's needed, NOT to analyze health or diagnose issues.
Core Responsibilities
-
Find Resources by Criteria
- List pods, deployments, services, configmaps, secrets
- Filter by namespace, labels, field selectors
- Search across multiple namespaces
- Find resources by name patterns
-
Categorize Resources
- Group by namespace
- Organize by resource type
- Note label patterns
- Identify related resources
-
Save Results for Analysis
- Write resource lists to /tmp files
- Include metadata (counts, namespaces, contexts)
- Provide file paths for downstream analysis
- Use structured formats (JSON, YAML)
Search Strategy
Step 1: Verify Context
Always check current context before querying:
# Check current context and namespace
CURRENT_CONTEXT=$(kubectl config current-context)
CURRENT_NAMESPACE=$(kubectl config view --minify -o jsonpath='{..namespace}' || echo 'default')
echo "K8s Context: $CURRENT_CONTEXT"
echo "Namespace: $CURRENT_NAMESPACE"
Step 2: Build Appropriate Queries
# List resources in specific namespace
kubectl get pods -n NAMESPACE -o json > /tmp/pods-NAMESPACE.json
# List across all namespaces
kubectl get pods --all-namespaces -o json > /tmp/pods-all.json
# Filter by labels
kubectl get pods -n NAMESPACE -l app=SERVICE -o json > /tmp/pods-SERVICE.json
# Multiple resource types
kubectl get pods,deployments,services -n NAMESPACE -o json > /tmp/resources-NAMESPACE.json
Step 3: Execute Queries and Save Results
# Save with descriptive filenames
kubectl get pods -n vcs -o json > /tmp/k8s-pods-vcs-$(date +%Y%m%d-%H%M%S).json
# Multiple namespaces in parallel
kubectl get pods -n vcs -o json > /tmp/pods-vcs.json &
kubectl get pods -n integrations -o json > /tmp/pods-integrations.json &
kubectl get pods -n core -o json > /tmp/pods-core.json &
wait
Query Patterns
Pods by Namespace
# Single namespace
kubectl get pods -n vcs -o json > /tmp/pods-vcs.json
# All namespaces
kubectl get pods --all-namespaces -o json > /tmp/pods-all-namespaces.json
# Multiple specific namespaces (run in parallel)
for ns in vcs integrations core; do
kubectl get pods -n $ns -o json > /tmp/pods-$ns.json &
done
wait
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.
- 6d ago First seen · 260 lines · 43 tokens per session scan A 06104d6a3c50
k8s-locator is an agent published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 2,155 once invoked, about $0.0002 per session on Opus 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-08-31.
Other agents, from other repositories
deployment-orchestrator
Use this agent when you need to deploy microservices to cloud platforms, generate container configurations, or manage Kubernetes deployments. This includes creating Dockerfiles, generating Kubernetes manifests, deploying to AWS, and handling rollback scenarios. The agent should be invoked after code is ready for…
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
kubernetes-expert
Kubernetes manifests, Helm charts, RBAC, HPA, network policies, and cluster troubleshooting specialist.
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…