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 skills add orcasecurity/orca-skills --skill orca-k8s-connector-troubleshootgit clone --depth 1 https://github.com/orcasecurity/orca-skillsWrote 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/orcasecurity/orca-skills/orca-k8s-connector-troubleshoot)<a href="https://agentmods.dev/skills/orcasecurity/orca-skills/orca-k8s-connector-troubleshoot"><img src="https://agentmods.dev/badge/skills/orcasecurity/orca-skills/orca-k8s-connector-troubleshoot/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/skills/orcasecurity/orca-skills/orca-k8s-connector-troubleshoot"><img src="https://agentmods.dev/badge/skills/orcasecurity/orca-skills/orca-k8s-connector-troubleshoot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 96 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Privilege Escalation · line 109 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 143 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 193 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 346 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00092 | $0.07742 |
| Opus 5.5 | $0.00037 | $0.03097 |
| Sonnet 5.5 | $0.00018 | $0.01548 |
| Haiku 4.5 | $0.00009 | $0.00774 |
Grade A, and why
orca-k8s-connector-troubleshoot 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. The tunnel-client image has no `curl` built in — test from a throwaway debug pod instead: `kubectl run tmp-curl --rm -it --image=curlimages/curl -n <namespace> -- curl -v https://<tunnelAddr>:443`. How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orca Kubernetes Connector Troubleshooting Skill
Answers: "Why isn't my Kubernetes Connector installing or connecting, and how do I fix it myself before opening a support ticket?"
Background
The Kubernetes Connector (aka K8s Tunnel Client, Helm chart orca-tunnel, image k8s-tunnel-client) runs entirely on the customer's own cluster. It opens a read-only outbound tunnel (built on frp) back to Orca so private and self-managed clusters can be scanned without exposing the cluster's API server to Orca. Because it runs on customer infrastructure, failures are invisible to Orca until the customer reports them. Most of what's covered here can be self-diagnosed from helm status, kubectl describe, and pod logs alone — that's the point of this skill.
Quick glossary (so the categories below don't have to re-explain these every time):
| Term | Means |
|---|---|
frp |
The open-source reverse-proxy library the tunnel is built on. TCP only — if a firewall log shows UDP traffic, that's unrelated noise, not the tunnel. |
| Tunnel target | Orca's server-side record of a specific cluster's tunnel. Can go stale (survive after the customer uninstalls the chart) and is only cleanable by Orca support/on-call. |
tunnelId / tunnelToken |
The credential pair from Orca's cluster-onboarding screen. Unique per cluster — never reuse one from a different cluster. |
cloudVendorId |
The cloud-vendor-specific cluster identifier (format varies by vendor — see the Connecting Clusters doc). The single most common typo source in install commands. |
| SCC | OpenShift's Security Context Constraint — its equivalent of a PodSecurityPolicy. |
Usage
/orca-k8s-connector-troubleshoot <paste error, helm status, kubectl describe, or pod logs output>
Or natural language:
- "the k8s connector pod is stuck in ImagePullBackOff"
- "helm install for orca-tunnel failed, here's the output: ..."
- "tunnel keeps disconnecting, logs show TLS handshake timeout"
- "cluster shows connected in Orca but no inventory data is showing up"
- "we're getting Unauthorized when the connector reads the cluster API"
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 · 348 lines · 92 tokens per session scan A f7e325f557e4
orca-k8s-connector-troubleshoot is a skill published in the GitHub repository orcasecurity/orca-skills (56 stars, last pushed 11d ago), licensed MIT. It adds 92 tokens to every session and 7,742 once invoked, about $0.0004 per session on Opus 5.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-08-30.
Other skills, from other repositories
app-platform-troubleshooting
Debug running App Platform applications by accessing containers, analyzing logs, running diagnostics, and applying fixes. Use when apps fail to deploy, crash at runtime, have connectivity issues, or need performance diagnosis.
mirrord-up
Helps users run multiple concurrent mirrord sessions from a single mirrord-up.yaml (compose-style multi-service local debugging). Use when the user mentions mirrord up, mirrord-up.yaml, mirrord up init, debugging several related microservices together, or managing multiple mirrord sessions' lifecycle in one command.
observability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
railway-debug
Analyze Railway production logs and debug deploy/runtime errors. Full workflow from log collection through root cause analysis, migration recovery, and post-deploy verification.
railway-logs
Fetch and diagnose Railway deployment logs for production issues. Use when an app or deploy on Railway is erroring. Triggers on: logs do railway, ver os logs, erro em producao, app caiu, deploy quebrou no railway, railway logs, production error.
python-project-deployment-troubleshooting
Read-only first troubleshooting workflow for Python project deployments, including systemd startup failures, dependency issues, encoding problems, permissions, proxy setup, and readiness gates.