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/echoqili/ssh-licco/ssh-mcp-setupnpx skills add Echoqili/ssh-licco --skill ssh-mcp-setupgit clone --depth 1 https://github.com/Echoqili/ssh-liccoWhat 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 | $0.00033 | $0.03310 |
| Opus 5 | $0.00016 | $0.01655 |
| Sonnet 5 | $0.00007 | $0.00662 |
| Haiku 4.5 | $0.00003 | $0.00331 |
Grade C, and why
ssh-mcp-setup scanned grade C 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.ssh-licco-venv How it starts
The opening of the file, as written. The whole thing — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Setup and Configuration Guide
Installation
Method 1: npx One-Click (Recommended, Zero Config)
npx ssh-licco
First run automatically: detect Python → create venv → install dependencies → verify integrity → start MCP server. No manual setup needed.
This creates an isolated Python venv at ~/.ssh-licco-venv and avoids all conflicts.
Method 2: From npm (Recommended for Windows)
npm install -g ssh-licco
Post-install script (install.js) auto-detects existing venv and performs incremental update.
Method 3: From PyPI
pip install ssh-licco
Method 4: From Source
git clone https://github.com/Echoqili/ssh-licco.git
cd ssh-licco
pip install -e .
Update Version
# npm
npm update -g ssh-licco
# pip
pip install --upgrade ssh-licco
Auto-Install System Architecture
ssh-licco uses a three-layer architecture for zero-config startup:
User → npx ssh-licco
↓
┌──── ssh-licco.js (Node Layer) ────┐
│ ① Find Python 3.10+ │
│ ② Detect Anaconda environment │
│ ③ Create/reuse ~/.ssh-licco-venv │
│ ④ pip install dependencies │
│ ⑤ Verify dependency integrity │
└──────────┬────────────────────────┘
↓
┌── cli.py (Python Entry) ──────┐
│ Only starts MCP server │
└──────────┬────────────────────┘
↓
┌── SSHMCPServer (MCP Service) ─┐
│ SSH connect, execute, etc. │
└───────────────────────────────┘
Smart Install Features
| Feature | Description |
|---|---|
| Anaconda Auto-Detect | Detects conda environment, uses isolated venv to avoid conflicts |
| Dependency Integrity Check | Verifies all dependencies on every startup, auto-repairs if missing |
| Incremental Update | Doesn't delete existing venv, uses pip install -e . for incremental install |
| Auto-Repair | Auto re-installs when dependencies are corrupted, no manual intervention |
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.
- 2d ago First seen · 459 lines · 33 tokens per session scan C 897b052770b4
ssh-mcp-setup is a skill published in the GitHub repository Echoqili/ssh-licco (3 stars, last pushed 14d ago), licensed MIT. It adds 33 tokens to every session and 3,310 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.