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 skills add muchiny/bridge-mcp --skill ssh-auditgit clone --depth 1 https://github.com/muchiny/bridge-mcpWrote 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/muchiny/bridge-mcp/ssh-audit)<a href="https://agentmods.dev/skills/muchiny/bridge-mcp/ssh-audit"><img src="https://agentmods.dev/badge/skills/muchiny/bridge-mcp/ssh-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/muchiny/bridge-mcp/ssh-audit"><img src="https://agentmods.dev/badge/skills/muchiny/bridge-mcp/ssh-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.00740 |
| Opus 5.5 | $0.00022 | $0.00296 |
| Sonnet 5.5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
ssh-audit 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 1mo 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Run security audits on a remote server via bridge-mcp CLI.
Delegation: Use a general-purpose agent (via the Agent tool) to run these commands in isolation, so verbose scan output does not pollute the main conversation.
Parse $ARGUMENTS: first word = host, second word (optional) = scope (default: quick).
Scope: quick (~2 min)
Fast security overview — run this first:
# Open ports
bridge-mcp tool ssh_port_scan host=HOST --json
# Certificate expiry
bridge-mcp tool ssh_cert_expiry host=HOST --json
# Fail2ban status
bridge-mcp tool ssh_fail2ban_status host=HOST --json
# Firewall rules
bridge-mcp tool ssh_firewall_list host=HOST --json
# Listening services
bridge-mcp tool ssh_exec host=HOST command="ss -tlnp" --json
Scope: network
Network-focused security assessment:
# SSL/TLS audit
bridge-mcp tool ssh_ssl_audit host=HOST --json
# Port scan
bridge-mcp tool ssh_port_scan host=HOST --json
# Active connections
bridge-mcp tool ssh_net_connections host=HOST --json
# DNS configuration
bridge-mcp tool ssh_net_dns host=HOST --json
Scope: compliance
Standards-based compliance check:
# CIS Benchmark
bridge-mcp tool ssh_cis_benchmark host=HOST --json
# STIG check
bridge-mcp tool ssh_stig_check host=HOST --json
# Compliance score
bridge-mcp tool ssh_compliance_score host=HOST --json
# Full compliance report
bridge-mcp tool ssh_compliance_report host=HOST --json
Scope: full
Comprehensive audit — combines all scopes plus vulnerability scanning:
Run all commands from quick, network, and compliance scopes, then add:
# SBOM generation
bridge-mcp tool ssh_sbom_generate host=HOST --json
# Vulnerability scan
bridge-mcp tool ssh_vuln_scan host=HOST --json
# SELinux / AppArmor status
bridge-mcp tool ssh_selinux_status host=HOST --json
bridge-mcp tool ssh_apparmor_status host=HOST --json
# Security audit log
bridge-mcp tool ssh_security_audit host=HOST --json
# User accounts review
bridge-mcp tool ssh_user_list host=HOST --json
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.
- 1mo ago First seen · 110 lines · 54 tokens per session scan A 2895f6a77d4a
ssh-audit is a skill published in the GitHub repository muchiny/bridge-mcp (10 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 740 once invoked, about $0.0002 per session on Opus 5.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
tianji-worker
Use when creating, testing, deploying, invoking, debugging, scheduling, pausing, or rolling back Tianji Workers, or managing their environment variables and shared modules.
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
gateway
Start and manage the Kurtosis gateway for Kubernetes. The gateway forwards local ports to the Kurtosis engine and services running in a k8s cluster. Required when using Kurtosis with Kubernetes. Use when kurtosis engine status shows nothing on k8s or services aren't reachable.
backup-recovery
Design and verify backups and restoration for owned databases, files and application state. Use when preparing recovery, migrating data or testing backups; protect the source and prove restore into an isolated destination before calling recovery ready.
cloudflare-workers
Build and maintain Cloudflare Workers with typed bindings, explicit compatibility and isolated validation. Use when implementing Workers handlers, integrating KV/R2/D1/Durable Objects/Queues or configuring Wrangler; deployment remains governed by the user task and target environment.
kubernetes-operations
Operate and deploy owned Kubernetes workloads with explicit cluster, namespace and rollout identity. Use when configuring Deployments, Services, probes, resources or diagnosing a known workload; do not expand an application task into uncontrolled cluster administration.