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/scitix/siclaw/hpa-debugnpx skills add scitix/siclaw --skill hpa-debuggit clone --depth 1 https://github.com/scitix/siclawWrote 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/scitix/siclaw/hpa-debug)<a href="https://agentmods.dev/skills/scitix/siclaw/hpa-debug"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/hpa-debug.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.00042 | $0.01399 |
| Opus 5 | $0.00021 | $0.00700 |
| Sonnet 5 | $0.00008 | $0.00280 |
| Haiku 4.5 | $0.00004 | $0.00140 |
Grade A, and why
hpa-debug 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 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.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HPA Autoscaling Failure Diagnosis
When a HorizontalPodAutoscaler is not scaling as expected — stuck at min/max replicas, showing <unknown> metrics, or not responding to load — follow this flow to identify the root cause.
Scope: This skill is for diagnosis only. Once you identify the root cause, report it to the user and stop. Do NOT attempt to modify HPA settings, resource requests, or metrics configuration — that should be left to the user.
Diagnostic Flow
1. Check HPA status
kubectl get hpa <hpa-name> -n <ns>
Note:
- TARGETS — current value vs target (e.g.,
80%/50%). If showing<unknown>/50%, metrics are unavailable. - MINPODS / MAXPODS — scaling bounds
- REPLICAS — current replica count
2. Describe the HPA
kubectl describe hpa <hpa-name> -n <ns>
Focus on:
- Conditions — look for
AbleToScale,ScalingActive, andScalingLimitedwith their status and reason - Events — scaling decisions, metric fetch errors, or rate-limiting messages
- Metrics — each metric's current value, target, and type (resource, custom, external)
3. Check metrics-server health
kubectl get pods -n kube-system -l k8s-app=metrics-server -o wide
If no pods are found, try:
kubectl get deployment -n kube-system metrics-server
Verify metrics-server is serving data:
kubectl top pods -n <ns>
If kubectl top returns error: Metrics API not available, metrics-server is not working.
4. Check target resource requests
HPA with CPU/memory percentage targets requires resources.requests to be set on the target containers.
kubectl get deployment <target-name> -n <ns> -o jsonpath='{range .spec.template.spec.containers[*]}{.name}: cpu={.resources.requests.cpu} memory={.resources.requests.memory}{"\n"}{end}'
If requests are not set, the HPA cannot calculate utilization percentages.
5. Match patterns and conclude
<unknown> metrics — Metrics not available
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 · 160 lines · 42 tokens per session scan A 581c54f80308
hpa-debug is a skill published in the GitHub repository scitix/siclaw (230 stars, last pushed 5d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,399 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-30.
Other skills, from other repositories
ariadne-kubernetes-graph
Use for Ariadne MCP-backed Kubernetes state questions: translate operational questions into Cypher, repair graphquery failures, and decide when graphschema or graphhealth is needed. Best for live or snapshot-backed graph data about resource relationships; do not use for codebase-only tasks or generic Kubernetes…
k8s-service-connectivity
Service 连通性问题通常由 Endpoints 缺失、Selector 不匹配、[[networkpolicy|NetworkPolicy]] 阻断或 kube-proxy 异常引起。.
k8s-dns-failure
DNS 解析问题诊断与修复：CoreDNS 是 Kubernetes 集群 DNS 的核心组件。DNS 问题会导致服务发现失败、外部依赖不可访问等连锁问题。.
k8s-deployment-rollout
Kubernetes Deployment 发布失败、滚动更新卡住的完整诊断-修复-验证 Skill.
k8s-pod-crashloop
Pod CrashLoopBackOff / OOMKilled 诊断与修复：Pod CrashLoopBackOff 和 OOMKilled 是 Kubernetes 工作负载中最常见的问题类型。本 Skill 覆盖从症状识别到修复验证的完整闭环。.
k8s-control-plane
Control Plane Failure：API entities/etcd.md/Scheduler 问题的诊断与修复 Skill。.