Borrowing it
Nothing to install: this file belongs to Echoqili/ssh-licco. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Echoqili/ssh-licco/master/.trae/skills/ssh-mcp-troubleshoot/SKILL.mdgit clone --depth 1 https://github.com/Echoqili/ssh-liccoWrote 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/echoqili/ssh-licco/ssh-mcp-troubleshoot)<a href="https://agentmods.dev/skills/echoqili/ssh-licco/ssh-mcp-troubleshoot"><img src="https://agentmods.dev/badge/skills/echoqili/ssh-licco/ssh-mcp-troubleshoot.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.00037 | $0.03740 |
| Opus 5 | $0.00018 | $0.01870 |
| Sonnet 5 | $0.00007 | $0.00748 |
| Haiku 4.5 | $0.00004 | $0.00374 |
Grade B, and why
ssh-mcp-troubleshoot scanned grade B 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo grep "PasswordAuthentication" /etc/ssh/sshd_config How it starts
The opening of the file, as written. The whole thing — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SSH MCP Troubleshooting Guide
Quick Diagnostics
Check SSH Connection
ping -c 4 43.143.207.242
nc -zv 43.143.207.242 22
telnet 43.143.207.242 22
Check Server Status
systemctl status sshd
systemctl status firewalld
iptables -L -n
df -h
free -m
uptime
Common Issues
1. Connection Timeout
Symptoms:
- "Connection timed out"
- "No route to host"
Solutions:
- Check server IP is correct
- Check server is running
- Check firewall allows SSH (port 22)
- Check server has network connectivity
- Try with longer timeout:
timeout=120
MCP Example:
连接 SSH,host=43.143.207.242, username=root, password=xxx, timeout=120
2. Authentication Failed
Symptoms:
- "Authentication failed"
- "Permission denied"
Solutions:
- Verify username is correct
- Verify password is correct
- Check SSH config:
PasswordAuthentication yes - Check user exists on server
- Check user has shell access:
grep username /etc/passwd
Server Commands:
sudo grep "PasswordAuthentication" /etc/ssh/sshd_config
sudo systemctl restart sshd
3. Error Reading SSH Protocol Banner
Symptoms:
- "Error reading SSH protocol banner"
- "Connection closed by remote host"
Solutions:
- SSH service may be hung - restart it:
sudo systemctl restart sshd - Check SSH service status:
sudo systemctl status sshd sudo journalctl -u sshd -n 50 - Check server load:
uptime top - Check SSH port is responding:
nc -zv hostname 22
4. Host Key Verification Failed
Symptoms:
- "Host key verification failed"
- "Known hosts file error"
Solutions:
- Remove old host key:
ssh-keygen -R hostname - Or use
accept_new_host_key=truein ssh_connect (testing only):连接 SSH,host=xxx, accept_new_host_key=true - Or disable strict checking (not recommended for production):
连接 SSH,host=xxx, strict_host_key_checking=false
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.
- 7d ago First seen · 526 lines · 37 tokens per session scan E f8b80b032ea9
ssh-mcp-troubleshoot is a skill published in the GitHub repository Echoqili/ssh-licco (3 stars, last pushed 20d ago), licensed MIT. It adds 37 tokens to every session and 3,740 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-handle-disruption-gpu-tpu
Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.