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 StarRocks/starrocks-debug-skills --skill deploymentgit clone --depth 1 https://github.com/StarRocks/starrocks-debug-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/starrocks/starrocks-debug-skills/deployment)<a href="https://agentmods.dev/skills/starrocks/starrocks-debug-skills/deployment"><img src="https://agentmods.dev/badge/skills/starrocks/starrocks-debug-skills/deployment/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/starrocks/starrocks-debug-skills/deployment"><img src="https://agentmods.dev/badge/skills/starrocks/starrocks-debug-skills/deployment.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.05780 |
| Opus 5.5 | $0.00031 | $0.02312 |
| Sonnet 5.5 | $0.00016 | $0.01156 |
| Haiku 4.5 | $0.00008 | $0.00578 |
Grade A, and why
deployment 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.
curl -s http://<fe_host>:8030/api/health How it starts
The opening of the file, as written. The whole thing — 593 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Troubleshooting
Investigation guide for FE and BE startup failures, port conflicts, BDB residual entries, JDK/JRE issues, and priority network configuration.
Six root causes account for the vast majority of startup failures:
- Cause A — Port conflict (FE or BE port already in use)
- Cause B — Missing directories or meta path does not exist
- Cause C — Multi-NIC /
priority_networksmisconfiguration - Cause D — Clock drift (NTP not synced, delta >5s)
- Cause E — BDB corruption or residual member entry
- Cause F — HMS blocking FE startup (external catalog configured but HMS unreachable)
Metric Taxonomy — Read This First
Before diagnosing, understand the observable signals for startup failures.
FE startup signals (fe.log)
| Signal | Meaning |
|---|---|
port xxx is used |
Port conflict — another process holds the port |
meta not exist |
FE meta directory missing — must be created before start |
Could not initialize class...BackendServiceProxy |
JRE installed instead of JDK; tools.jar missing |
Fe type:unknown, is ready:false + current node is not added |
FE not registered — run ALTER SYSTEM ADD FOLLOWER/OBSERVER first |
backend ip saved in master does not equal to backend local ip |
Wrong NIC selected — set priority_networks |
this replica exceeds max permissible delta:5000ms |
Clock skew between FE nodes >5s — sync NTP |
connection refused on http_port |
Network partition between FE nodes or wrong port in fe.conf |
Finished replaying journal absent after >60s |
BDB journal replay stuck or HMS blocking startup |
BDB environment setup failed / LogFileNotFoundException |
BDB corruption — requires recovery |
It conflicts with the socket already used by the member |
BDB sees stale member entry — DbGroupAdmin -removeMember |
Start to connect to Hive metastore + no Connected |
HMS unreachable, blocking FE catalog init |
BE startup signals (be.log)
What ships with it
4 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.
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 · 593 lines · 78 tokens per session scan A 8022ab96c6fa
deployment is a skill published in the GitHub repository StarRocks/starrocks-debug-skills (77 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 5,780 once invoked, about $0.0003 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
k8s-incident
Respond to Kubernetes incidents with runbooks and diagnostics. Use for outages, pod failures, node issues, network problems, and emergency response.
k8s-troubleshoot
Debug Kubernetes pods, nodes, and workloads. Use when pods are failing, containers crash, nodes are unhealthy, or users mention debugging, troubleshooting, or diagnosing Kubernetes issues.
k8s-cilium
Cilium and Hubble network observability for Kubernetes. Use when managing network policies, observing traffic flows, or troubleshooting connectivity with eBPF-based networking.
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.
doris-debug-deployment
Use for Doris FE/BE startup failures, port conflicts, prioritynetworks misrouting, metadir corruption, and ADD/DROP BACKEND issues.
debugging-workflows
Systematic troubleshooting for Falcon Foundry CLI errors, manifest validation failures, deploy failures, artifact runtime errors, and development server issues. TRIGGER when user encounters CLI errors, foundry ui run not working, deploy failures, authentication issues, function execution failures, "debug my function"…