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 skills/adrielp/ai-engineering-harness/debug-k8snpx skills add adrielp/ai-engineering-harness --skill debug-k8sgit clone --depth 1 https://github.com/adrielp/ai-engineering-harnessWrote 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/skills/adrielp/ai-engineering-harness/debug-k8s)<a href="https://agentmods.dev/skills/adrielp/ai-engineering-harness/debug-k8s"><img src="https://agentmods.dev/badge/skills/adrielp/ai-engineering-harness/debug-k8s.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 | $0.00019 | $0.01181 |
| Opus 5 | $0.00010 | $0.00590 |
| Sonnet 5 | $0.00004 | $0.00236 |
| Haiku 4.5 | $0.00002 | $0.00118 |
Grade A, and why
debug-k8s 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 5d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Kubernetes
You are tasked with helping debug Kubernetes issues. This command allows you to investigate problems by examining pods, logs, events, and cluster state without making changes.
MCP Server Preference
When the Kubernetes MCP server is available, prefer using MCP tools:
mcp__kubernetes__list_pods- List pods in a namespacemcp__kubernetes__get_pod- Get pod detailsmcp__kubernetes__get_logs- Get pod logsmcp__kubernetes__list_events- List cluster eventsmcp__kubernetes__describe_resource- Describe any resource
When MCP is unavailable, fall back to kubectl commands via Bash.
To check if MCP is available, attempt an MCP tool first. If it fails with "tool not found", use kubectl.
Initial Response
When invoked WITH a context (namespace, pod name, or resource):
I'll help debug Kubernetes issues with [resource]. Let me check the cluster state.
What specific problem are you encountering?
- Pod not starting?
- Application errors?
- Network/connectivity issues?
- Resource constraints?
I'll investigate the pods, logs, and events to help identify the issue.
When invoked WITHOUT parameters:
I'll help debug your Kubernetes issue.
Please provide some context:
- Which namespace?
- Which pod/deployment/service?
- What's the expected vs actual behavior?
I can investigate pod status, logs, events, and resource state.
Process Steps
Step 1: Understand the Problem
- Get context from user (namespace, resource name, symptoms)
- Quick cluster check:
- Current kubectl context
- Target namespace
Step 2: Investigate the Issue
Spawn parallel Task agents based on the problem type:
Task 1 - Pod Status:
Check pod status and conditions
- List pods in namespace
- Get pod details (phase, conditions, container status)
Return: Pod state summary, restart counts, readiness
Task 2 - Pod Logs:
Examine recent logs for errors
- Get logs from main container
- Check previous container logs if restarted
Return: Key errors/warnings with timestamps
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.
- 5d ago First seen · 191 lines · 19 tokens per session scan A c3555819e78d
debug-k8s is a skill published in the GitHub repository adrielp/ai-engineering-harness (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,181 once invoked, about $0.0001 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-30.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.