Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JansenAnalytics/claudexnpx agentmods add skills/jansenanalytics/claudex/ssh-remoteWrote 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/jansenanalytics/claudex/ssh-remote)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/ssh-remote"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/ssh-remote.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.00029 | $0.01218 |
| Opus 5 | $0.00015 | $0.00609 |
| Sonnet 5 | $0.00006 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade B, and why
ssh-remote 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 4d 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.
| Permission denied (publickey) | Check key permissions: `chmod 600 ~/.ssh/key`, `chmod 700 ~/.ssh` | How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ssh-remote
SSH into remote servers, execute commands, transfer files via SCP/rsync, manage SSH keys and configs, tunnel ports.
When to Use
- Deploying to remote servers
- Managing VPS instances
- Transferring files (SCP/rsync)
- Setting up SSH tunnels or port forwarding
- Configuring SSH keys and agent forwarding
- Running remote commands or scripts
Quick Reference
Connect to a Server
ssh user@host
ssh -i ~/.ssh/mykey user@host -p 2222
Execute Remote Command
ssh user@host 'command here'
ssh user@host 'bash -s' < local-script.sh
File Transfer
# SCP
scp local-file user@host:/remote/path
scp user@host:/remote/file ./local-path
scp -r local-dir/ user@host:/remote/path/
# Rsync (preferred for large transfers)
rsync -avz --progress local-dir/ user@host:/remote/path/
rsync -avz --delete local-dir/ user@host:/remote/path/ # mirror
rsync -avz -e 'ssh -p 2222' local/ user@host:/remote/
SSH Tunnels
# Local forward: access remote:3306 via localhost:3306
ssh -L 3306:localhost:3306 user@host
# Remote forward: expose local:8080 on remote:9090
ssh -R 9090:localhost:8080 user@host
# SOCKS proxy
ssh -D 1080 user@host
# Background tunnel
ssh -fNL 3306:localhost:3306 user@host
Key Management
# Generate key
ssh-keygen -t ed25519 -C "comment" -f ~/.ssh/keyname
# Copy key to server
ssh-copy-id -i ~/.ssh/keyname.pub user@host
# Add to agent
eval $(ssh-agent)
ssh-add ~/.ssh/keyname
# Test connection
ssh -T user@host
Scripts
| Script | Purpose |
|---|---|
scripts/ssh-config-gen.sh |
Generate/update SSH config entries |
scripts/key-rotation.sh |
Rotate SSH keys on remote hosts |
scripts/tunnel-manager.sh |
Manage persistent SSH tunnels |
scripts/rsync-deploy.sh |
Deploy files via rsync with backup |
Workflows
1. Set Up New Server Access
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.
- 4d ago First seen · 200 lines · 29 tokens per session scan B cdbc3b0b5ab8
ssh-remote is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,218 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
lambda-gpu-cloud
Safely inspect and operate Lambda Cloud GPU instances through the documented Cloud API and SSH, with explicit approval before billable or destructive actions.
runpod-gpu-cloud
Safely inspect and operate RunPod resources with runpodctl, live product data, and explicit approval before paid or destructive actions.
tensorpool-gpu-cloud
Safely inspect and operate TensorPool GPU clusters and jobs using the current tp CLI, with explicit approval before any billable or destructive action.
vast-ai-gpu-cloud
Safely inspect and operate Vast.ai marketplace instances with the vastai CLI, live offer data, and explicit approval before paid or destructive actions.
implementing-envelope-encryption-with-aws-kms
Envelope encryption is a strategy where data is encrypted with a data encryption key (DEK), and the DEK itself is encrypted with a master key (KEK) managed by AWS KMS. This approach allows encrypting.
performing-ssl-certificate-lifecycle-management
SSL/TLS certificate lifecycle management encompasses the full process of requesting, issuing, deploying, monitoring, renewing, and revoking X.509 certificates. Poor certificate management is a leading.