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/muchiny/bridge-mcp/ssh-deploynpx skills add muchiny/bridge-mcp --skill ssh-deploygit clone --depth 1 https://github.com/muchiny/bridge-mcpWhat 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.00061 | $0.00754 |
| Opus 5 | $0.00030 | $0.00377 |
| Sonnet 5 | $0.00012 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
ssh-deploy 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 2d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Operations
Deploy changes to remote infrastructure via bridge-mcp CLI.
This skill is manual-only — invoke with /ssh-deploy.
Parse $ARGUMENTS: first word = host, second word = action (restart, canary, rolling, k8s, helm).
Pre-Deploy Checklist
Before ANY deployment, verify:
-
Health check — confirm the target is healthy BEFORE changing anything:
bridge-mcp tool ssh_diagnose host=HOST --json -
Confirm with user — always ask before proceeding with destructive operations.
-
Know the rollback — have a rollback command ready before executing.
Deployment Patterns
Service Restart
# Check current status
bridge-mcp tool ssh_service_status host=HOST service=SERVICE --json
# Restart
bridge-mcp tool ssh_service_restart host=HOST service=SERVICE
# Verify recovery
bridge-mcp tool ssh_service_status host=HOST service=SERVICE --json
Canary Deploy
Deploy to a single canary host first, verify, then decide:
# Execute on canary
bridge-mcp tool ssh_canary_exec host=HOST command="DEPLOY_COMMAND"
# Health check canary
bridge-mcp tool ssh_diagnose host=HOST --json
# ASK the user before continuing to remaining hosts
Rolling Deploy
Execute on one host at a time with health checks between:
bridge-mcp tool ssh_rolling_exec host=HOST command="DEPLOY_COMMAND"
Kubernetes Rollout
# Check current state
bridge-mcp tool ssh_k8s_get host=HOST resource=deployments namespace=NAMESPACE --json
# Apply update
bridge-mcp tool ssh_k8s_apply host=HOST manifest="PATH_TO_YAML" namespace=NAMESPACE
# Watch rollout
bridge-mcp tool ssh_k8s_rollout host=HOST action=status deployment=DEPLOYMENT namespace=NAMESPACE
# Rollback if needed
bridge-mcp tool ssh_k8s_rollout host=HOST action=undo deployment=DEPLOYMENT namespace=NAMESPACE
Helm Upgrade
# Check current release
bridge-mcp tool ssh_helm_status host=HOST release=RELEASE --json
# Upgrade
bridge-mcp tool ssh_helm_upgrade host=HOST release=RELEASE chart=CHART
# Verify
bridge-mcp tool ssh_helm_status host=HOST release=RELEASE --json
# Rollback if needed
bridge-mcp tool ssh_helm_rollback host=HOST release=RELEASE
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.
- 2d ago First seen · 117 lines · 61 tokens per session scan A 810d1db17b04
ssh-deploy is a skill published in the GitHub repository muchiny/bridge-mcp (8 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 754 once invoked, about $0.0003 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
eu-ai-act-compliance
EU AI Act compliance logging and requirements. Use this skill when ensuring transparency, human oversight, and record-keeping per Regulation (EU) 2024/1689 — even if they just say "add compliance logging" or "make sure this is EU AI Act compliant". Not for security-code-auditor, privacy-first.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.