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/oaslananka/ssh-mcp-pro/ssh-operationsnpx skills add oaslananka/ssh-mcp-pro --skill ssh-operationsgit clone --depth 1 https://github.com/oaslananka/ssh-mcp-proWrote 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/oaslananka/ssh-mcp-pro/ssh-operations)<a href="https://agentmods.dev/skills/oaslananka/ssh-mcp-pro/ssh-operations"><img src="https://agentmods.dev/badge/skills/oaslananka/ssh-mcp-pro/ssh-operations.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 | $0.00033 | $0.00203 |
| Opus 5 | $0.00016 | $0.00102 |
| Sonnet 5 | $0.00007 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
ssh-operations 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 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.
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.
What it actually says
SSH Operations Skill
Use this skill when an agent needs to inspect or operate remote hosts through ssh-mcp-pro.
Workflow
- Identify the target host and confirm it is reachable.
- Treat the first pass as read-only diagnostics unless the user explicitly approves changes.
- Prefer purpose-built SSH MCP tools for host, session, process, file, service, log, tunnel, and metric operations.
- Before any file, service, privilege, tunnel, or process mutation, state the exact action, expected impact, and rollback path.
- After every action, report evidence: target host, tool used, outcome, and remaining risk.
Safety
Do not assume SSH access equals permission to modify production. Require explicit approval for privileged, destructive, service-affecting, or persistent 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.
- 4d ago First seen · 21 lines · 33 tokens per session scan A ad7bed647a14
ssh-operations is a skill published in the GitHub repository oaslananka/ssh-mcp-pro (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 203 once invoked, about $0.0002 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
scaled-swarm-predict
Large-scale social simulation with 50-200 demographically diverse AI personas debating on a simulated Twitter/Reddit board to predict outcomes.
swarm-predict
Multi-perspective risk analysis using structured persona debate before deploying changes.
spec-driven-development
Build software via spec-driven development (github/spec-kit). Whenever the user asks for a feature larger than a one-line tweak, scaffold a spec-kit project, capture WHAT + WHY, declare tech stack, break into tasks, then iterate the implementation until tests pass.
deploy-ai-agent
Deploy and manage AI agent workloads with GPU checks, API key management, and health monitoring.
app-deployer
Deploy and manage user applications as managed systemd services.
generation-timeline
NixOS generation-aware debugging and time-travel. Correlate system state changes with application failures. Query "what changed and when.".