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/hunchom/claude-code-ssh/operating-ssh-fleetnpx skills add hunchom/claude-code-ssh --skill operating-ssh-fleetgit clone --depth 1 https://github.com/hunchom/claude-code-sshWhat 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.00118 | $0.02696 |
| Opus 5 | $0.00059 | $0.01348 |
| Sonnet 5 | $0.00024 | $0.00539 |
| Haiku 4.5 | $0.00012 | $0.00270 |
Grade A, and why
operating-ssh-fleet scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating the SSH Fleet
Overview
ssh-manager is an MCP server that exposes 13 fat verb-tools (ssh_*) for operating a fleet of configured servers. Each tool covers one domain and multiplexes many operations through an action enum.
Core principle: For any server in the configuration, the ssh_* tools are the intended way to operate it — not raw ssh/scp/rsync through Bash. They are not a read-only convenience layer; they are the operator interface.
When to use
- Running, scripting, or backgrounding a command on a configured server
- Moving, reading, editing, or deploying files
- Reading or following logs; checking health, services, processes
- Databases, backups, Docker, tunnels, port probes, persistent sessions
- Multi-step changes across one or more servers
- Any time you would otherwise type
ssh host "...",scp, orrsyncin Bash for a configured host
When NOT to use
- The host is not in the configuration → raw
sshin Bash is fine. Runssh_fleetaction: serversto see what is configured. - Pure local work with no remote target.
The discipline: ssh_* over raw ssh
| Raw Bash | Why the tool wins |
|---|---|
ssh host "cmd" reconnects every call |
Tools hold a pooled connection — no per-call handshake |
ssh host journalctl dumps everything |
Output is head+tail truncated + compressed — won't flood context |
ssh host with inline password leaks on argv |
Credentials go via stdin/env, never ps-visible |
| Raw terminal dump | Structured results — per-segment exit codes, typed snapshots, sha256-verified transfers |
Violating the letter (using raw ssh "just this once") is violating the spirit. If the host is configured, use the tool.
The 13 tools
Always loaded. Pick the tool, then the action.
| Tool | Group | Actions | Replaces |
|---|---|---|---|
ssh_run |
core | exec, sudo, script, fleet, detach, job-status, job-kill | ssh host "cmd" |
ssh_find |
core | grep, locate, ls | ssh host "grep -rn …" |
ssh_file |
core | upload, download, sync, read, write, edit, diff, deploy, deploy-artifact | scp, cat > f <<EOF |
ssh_logs |
core | tail, follow-start, follow-read, follow-stop, journal | ssh host journalctl / tail -f |
ssh_service |
ops | status, start, stop, restart, enable, disable | ssh host systemctl … |
ssh_health |
ops | check, watch, procs, alerts | ssh host top/df/free |
ssh_db |
ops | query, list, dump, import | ssh host "mysql -e …" |
ssh_backup |
ops | create, list, restore, schedule | ssh host "tar/mysqldump …" |
ssh_docker |
ops | ps, logs, exec, restart, inspect | ssh host "docker …" |
ssh_session |
advanced | start, send, list, close, replay, memory | repeated ssh host "cmd" |
ssh_net |
advanced | tunnel-open, tunnel-list, tunnel-close, port-test | ssh -L/-R/-D, nc -z |
ssh_fleet |
advanced | servers, groups, aliases, command_alias, profiles, hooks, keys, history, connections | ssh -G, ~/.ssh/config |
ssh_plan |
advanced | run, approve | hand-sequenced batch of calls |
What ships with it
1 file 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.
- 2d ago First seen · 126 lines · 118 tokens per session scan A b1322006287d
operating-ssh-fleet is a skill published in the GitHub repository hunchom/claude-code-ssh (2 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session and 2,696 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
terraform-skill
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code…
huggingface-spaces
Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.