ssh-licco: Skill for Claude Code

.trae/skills/ssh-mcp-troubleshoot/SKILL.md

ssh-mcp-troubleshoot is a skill for Claude Code, Codex from Echoqili/ssh-licco. It costs 37 tokens per session (3,740 once invoked), scanned B, original, MIT.

A troubleshooting guide for SSH connections and ssh-licco startup problems.

In plain words
What is it for?
Use it to check network access, SSH service status, authentication settings, firewalls, and server resource or startup problems.
Why use it?
It helps diagnose common failures such as timeouts, rejected logins, blocked ports, and protocol or Docker issues.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is Echoqili/ssh-licco's own configuration. It tells Claude Code and Codex how to work on ssh-licco itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ssh-licco configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Echoqili/ssh-licco/master/.trae/skills/ssh-mcp-troubleshoot/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Echoqili/ssh-licco

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ssh-mcp-troubleshoot

README.md
[![agentmods](https://agentmods.dev/badge/skills/echoqili/ssh-licco/ssh-mcp-troubleshoot.svg)](https://agentmods.dev/skills/echoqili/ssh-licco/ssh-mcp-troubleshoot)
Your own site
<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>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,740 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Sonnet 5 · 7 Sept 2026 📄 Read the review
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash f8b80b032ea9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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
.trae/skills/ssh-mcp-troubleshoot/SKILL.md · 526 lines

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:

  1. Check server IP is correct
  2. Check server is running
  3. Check firewall allows SSH (port 22)
  4. Check server has network connectivity
  5. 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:

  1. Verify username is correct
  2. Verify password is correct
  3. Check SSH config: PasswordAuthentication yes
  4. Check user exists on server
  5. 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:

  1. SSH service may be hung - restart it:
    sudo systemctl restart sshd
    
  2. Check SSH service status:
    sudo systemctl status sshd
    sudo journalctl -u sshd -n 50
    
  3. Check server load:
    uptime
    top
    
  4. Check SSH port is responding:
    nc -zv hostname 22
    

4. Host Key Verification Failed

Symptoms:

  • "Host key verification failed"
  • "Known hosts file error"

Solutions:

  1. Remove old host key:
    ssh-keygen -R hostname
    
  2. Or use accept_new_host_key=true in ssh_connect (testing only):
    连接 SSH,host=xxx, accept_new_host_key=true
    
  3. Or disable strict checking (not recommended for production):
    连接 SSH,host=xxx, strict_host_key_checking=false
    

Read the full file on GitHub · 526 lines

Changes

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.

  1. 7d ago First seen · 526 lines · 37 tokens per session scan E f8b80b032ea9

Subscribe to this mod's changes

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.

Related

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…

google/skills · 83 tokens

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.

google/skills · 69 tokens

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…

google/skills · 112 tokens

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…

google/skills · 117 tokens

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.

awslabs/mcp · 52 tokens

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.

opensandbox-group/OpenSandbox · 48 tokens