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/openshift-eng/ai-helpers/nodenpx skills add openshift-eng/ai-helpers --skill nodegit clone --depth 1 https://github.com/openshift-eng/ai-helpersWrote 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/openshift-eng/ai-helpers/node)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/node"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/node.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.00108 | $0.00171 |
| Opus 5 | $0.00054 | $0.00086 |
| Sonnet 5 | $0.00022 | $0.00034 |
| Haiku 4.5 | $0.00011 | $0.00017 |
Grade A, and why
node 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 yesterday.
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.
allowed-tools: Bash(curl:*) What it actually says
How to use this skill
- Read references/INDEX.md to route to the relevant reference
- Read the reference, then act on it — run scripts, fetch data, present results
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/deployment/debug-binary.md 5.2 KB
- references/deployment/debug-binary/crio.md 6.6 KB
- references/deployment/debug-binary/cross-compile.md 4.5 KB
- references/deployment/debug-binary/deploy.md 10 KB
- references/deployment/debug-binary/ssh-bastion.md 4.8 KB
- references/development/crio-dev.md 1.4 KB
- references/development/crun-conmon.md 1.5 KB
- references/development/kubelet-dev.md 1.0 KB
- references/development/kueue-operator-dev.md 945 B
- references/development/mco-dev.md 1.7 KB
- references/development/worktrees.md 2.2 KB
- references/INDEX.md 933 B
- references/jira.md 9.1 KB
- references/platform-docs.md 1.1 KB
- references/prometheus.md 1.9 KB
- references/SETUP.md 2.2 KB
- references/shared/components.md 4.3 KB
- references/shared/team-info.md 4.0 KB
- references/shared/version-map.md 1.1 KB
- references/support.md 1.8 KB
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.
- yesterday First seen · 11 lines · 108 tokens per session scan A e7edcabc1f9d
node is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed yesterday), licensed Apache-2.0. It adds 108 tokens to every session and 171 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
image-pull-debug
Diagnose container image pull failures (ErrImagePull / ImagePullBackOff). Checks pod status, containerd logs, and events to identify root cause.
pod-pending-debug
Diagnose pod scheduling failures (Pending, Unschedulable). Checks events, node resources, taints, affinity, and PVC bindings to identify why a pod cannot be scheduled.
gke-workload-troubleshooting
Systematic Standard Operating Procedure (SOP) for diagnosing GKE workload failures, crash loops, resource OOMs, mounting errors, and connectivity timeouts.
kubernetes-specialist
Use when managing Kubernetes clusters, debugging Pods and workloads, designing Helm charts, reviewing manifests, or improving deployment, scaling, and observability practices.
archestra-dev-investigate
Use when investigating Archestra bugs or incidents — staging issues, backend 50x errors, Drizzle failed queries, DB connection pressure, deploy regressions, or Kubernetes/runtime symptoms. Orientation only; defers the process to /investigate.
diag-k8s-pod-crashloop
K8s Pod CrashLoopBackOff 全链排查。从 kubectl describe → events → logs → restart policy → resource limits → liveness/readiness probe → image pull → configmap/secret 挂载，定位根因并输出修复建议。.