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/kinothe-kafkaesque/ssh-mcp-server/agents-mdgit clone --depth 1 https://github.com/KinoThe-Kafkaesque/ssh-mcp-serverWrote 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/kinothe-kafkaesque/ssh-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/kinothe-kafkaesque/ssh-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/kinothe-kafkaesque/ssh-mcp-server/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.1 | $0.00540 | $0.00540 |
| Opus 5 | $0.00270 | $0.00270 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
ssh-mcp-server AGENTS.md 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 5d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This is a TypeScript MCP server for SSH and rsync operations. Runtime source lives in src/, with src/index.ts currently containing the MCP server setup, tool schemas, SQLite credential storage, and command execution handlers. Compiled JavaScript is emitted to build/ by TypeScript and should be treated as generated output. Root configuration includes package.json, package-lock.json, and tsconfig.json. Documentation lives in root Markdown files such as README.md.
Build, Test, and Development Commands
npm install: install runtime and development dependencies frompackage-lock.json.npm run build: compilesrc/**/*.tstobuild/usingtsc; run this before shipping changes.npm start: run the built server withnode build/index.jsover stdio.npx tsc --noEmit: optional type-check-only pass when you do not want to updatebuild/.
There is currently no npm test script. Until a test harness is added, npm run build is the minimum verification step.
Coding Style & Naming Conventions
Use TypeScript with strict mode enabled. Keep indentation at 4 spaces to match the existing source. Prefer clear camelCase names for functions and variables, PascalCase for interfaces and types, and snake_case only for MCP tool names such as ssh_exec and rsync_copy. Keep tool schemas and handler argument types aligned when adding or changing tools.
Testing Guidelines
Add tests when changing command construction, path validation, database behavior, or MCP tool schemas. Prefer focused tests around pure helpers and command-building logic before integration tests that touch real SSH hosts. Name tests after the behavior under test, for example validatePrivateKeyPath.test.ts or rsyncCommand.test.ts, and wire them into a future npm test script.
Commit & Pull Request Guidelines
Recent commits use short imperative subjects such as Update README, Add Dockerfile, and rsync fix. Prefer descriptive imperative messages, for example Fix rsync remote path quoting. Pull requests should describe the tool behavior changed, list local verification commands, and mention any SSH, SQLite, Docker, or Smithery impact.
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.
- 5d ago First seen · 31 lines · 540 tokens per session scan A 43ec76c77a17
ssh-mcp-server AGENTS.md is an instructions file published in the GitHub repository KinoThe-Kafkaesque/ssh-mcp-server (10 stars, last pushed 4mo ago), licensed MIT. It adds 540 tokens to every session, about $0.0027 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 instructions, from other repositories
rekal AGENTS.md
Instructions for janbjorge/rekal, covering rekal: agent instructions, what this project is, architecture, key rules and re-expansion bar.
Vault-Agent-Memory AGENTS.md
Instructions for zycaskevin/Vault-Agent-Memory, covering agent instructions for vault agent memory, common install architecture, second decision: optional features, first decision: database scope and safe agent workflow.
rekal CLAUDE.md
Instructions for janbjorge/rekal, a project described as: Long-term memory for LLMs. MCP server backed by hybrid search in a single SQLite file.
zen CLAUDE.md
Claude Code instructions for sheshbabu/zen, covering claude.md, development commands, build commands, dependencies and go build tags.
db-mcp copilot-instructions.md
Copilot instructions for neverinfamous/db-mcp, covering db-mcp — copilot code review context, project overview, session context, coding standards and naming.
state-memory-mcp copilot-instructions.md
Instructions for putervision/state-memory-mcp, covering state memory (state-memory-mcp), 1. priority order, 2. when to write to the graph, 3. workflow pattern and 4. codebase seeding on initialization.