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 instructions/oaslananka/ssh-mcp-pro/agents-mdgit 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/instructions/oaslananka/ssh-mcp-pro/agents-md)<a href="https://agentmods.dev/instructions/oaslananka/ssh-mcp-pro/agents-md"><img src="https://agentmods.dev/badge/instructions/oaslananka/ssh-mcp-pro/agents-md.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.01363 | $0.01363 |
| Opus 5 | $0.00681 | $0.00681 |
| Sonnet 5 | $0.00273 | $0.00273 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade B, and why
ssh-mcp-pro AGENTS.md 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.
directs the agent to use explain mode or policy resources and to call out sudo needs, destructive operations, path policy, rollback, commands, and files that How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - ssh-mcp-pro
Guidance for AI agents using ssh-mcp-pro v2.
Quick Start
{
"name": "ssh-mcp-pro",
"command": "ssh-mcp-pro",
"type": "stdio"
}
Secure Defaults
- Host-key verification is strict by default.
- Root SSH login is denied unless policy allows it.
- Raw
proc_sudois denied unless policy allows it. - Destructive commands and filesystem operations are policy-controlled.
- Use
policyMode: "explain"before mutations when you need a plan or user confirmation.
Recommended Workflow
ssh_list_configured_hoststo discover aliases when useful.ssh_open_sessionwithhostKeyPolicy: "strict"orexpectedHostKeySha256.os_detectto learn platform capabilities.- Read
ssh-mcp-pro://policy/effectivebefore privileged or destructive work. - Use task tools:
fs_*,proc_exec,ensure_*,file_*,tunnel_*. ssh_close_sessionwhen work is complete.
Explain Mode
Use explain mode when a request may mutate a remote host, change files, start or stop services, install packages, open tunnels, or require user approval before execution. Explain mode is a planning and policy-preview path; it is not a permission bypass and it does not execute the requested mutation.
Use policyMode: "explain" when you need a non-mutating preview from normal SSH
tools. For example, ssh_open_session with policyMode: "explain" returns a
connection plan with wouldConnect instead of opening a live SSH connection.
Write, transfer, process, ensure, and tunnel tools that honor the session policy
mode return explain-only plans instead of performing the change.
Use policyMode: "enforce" only after the plan has been reviewed, the target
host and path are correct, strict host-key verification is active, and the
effective policy allows the concrete operation. Enforce mode is the default mode
for actual work.
Connector clients can use ssh_policy_explain before opening sessions or
running task tools. It evaluates an optional hostAlias, action class, command,
and path against policy, returns executed: false, includes the policy
decision, and marks non-inspection requests as requiring explicit user
confirmation.
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 · 128 lines · 1,363 tokens per session scan B c7d49866d51b
ssh-mcp-pro AGENTS.md is an instructions file published in the GitHub repository oaslananka/ssh-mcp-pro (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,363 tokens to every session, about $0.0068 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-08-31.
Other instructions, from other repositories
clum AGENTS.md
Instructions for tddh/clum, covering clum 项目开发规则, mcp 工具使用规则(最高优先级), 开发规范, 项目结构 and 常用命令.
aiops-mcp AGENTS.md
AGENTS.md instructions for rmednitzer/aiops-mcp, covering agents.md, one-line, repo map, hard rules and build and test.
os-moda CLAUDE.md
Instructions for bolivian-peru/os-moda, covering claude.md - osmoda, what this is, current state, architecture (3 trust tiers) and components.
Rail-Connector-MCP AGENTS.md
AGENTS.md instructions for SNComrade/Rail-Connector-MCP, covering agent instructions, engineering rules and required checks.
coolify-mcp CLAUDE.md
Claude Code instructions for jurislm/coolify-mcp, covering claude.md, project overview, commands, run locally and architecture.
coolify-mcp copilot-instructions.md
Copilot instructions for jurislm/coolify-mcp, covering copilot instructions for coolify-mcp, project overview, git workflow, version numbers and build & test.