ssh-terminal
Skill0 starsChanged 53 days agoMITView on GitHub
Non-interactive SSH batch command execution (auth / timeout / audit). Use when: running non-interactive commands on an authorized server, capturing output, or batch inspection. Boundary: reject unauthorized hosts; no interactive shell.
In this repository27 other files it gives its agents.
- mysql-opsSkill
- redis-opsSkill
- data-opsSkill
- docker-containerSkill
- docker-imageSkill
- docker-installSkill
- docker-opsSkill
- apt-repoSkill
- file-opsSkill
- server-settingsSkill
- shell-execSkill
- infra-opsSkill
- bbrSkill
- firewallSkill
- net-secSkill
- ssh-keysSkill
- monitorSkill
- process-manageSkill
- obs-opsSkill
- opsSkill
- lnmpSkill
- nginx-rewriteSkill
- php-manageSkill
- reverse-proxySkill
- site-manageSkill
- web-stackSkill
- ssl-manageSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Every decision and exit code logged to ~/.opsctl/audit.log
- Distinctive: line 29
All input passes the same case-insensitive dangerous-command blacklist as the gate.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ssh-terminal
Capabilities (engine status)
- Key / agent auth (
BatchMode=yes, no password prompt) - Non-interactive batch command execution + stdout/stderr capture
- Connect timeout
ConnectTimeout=10+ total timeout 120s to avoid hangs
Safety gate
- Credentials read only from local
~/.opsctl/hosts.json(key file mode 600 recommended) - Reject unauthorized hosts (unknown host name errors out)
- Every decision and exit code logged to
~/.opsctl/audit.log
EXECUTION (real engine)
The engine is ssh <host> <cmd> — no pty, no interactive shell / multi-session UI.
For non-interactive batch tasks use shell-exec (--mode auto or --mode yes):
opsctl shell-exec --host web1 --cmd "uptime; free -h" --mode auto
opsctl shell-exec --host web1 --cmd "nginx -t" --mode auto⚠️ Do not pass --cmd "bash": stdin has no pty and will wait until the 120s timeout kills it.
All input passes the same case-insensitive dangerous-command blacklist as the gate.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.