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-auditnpx 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.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.00054 | $0.00740 |
| Opus 5 | $0.00027 | $0.00370 |
| Sonnet 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 3d 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.
- 3d 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 (8 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 740 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
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
redteam-cloud-detail-pack
Domain routing and boundary guidance for authorized cloud security testing, including IAM misconfiguration, exposed storage, metadata services, and serverless injection. Use when a task belongs to the cloud testing domain and needs scope, evidence, pivot, or exit criteria.
pinme-r2
Use when a PinMe Cloudflare Worker needs R2 object storage, including secure file or image upload, streaming download, metadata lookup, deletion, listing, Range requests, or R2+D1 coordination. Guides AI to use PinMe's automatically injected env.R2 binding without R2 credentials or manual Wrangler configuration.
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
pinme
Use this skill when the user mentions "pinme", or needs to upload files, store to IPFS, create/publish/deploy websites or full-stack services (including frontend pages, backend APIs, database storage, email sending, etc.), or any feature requiring backend database/server support.
cloudflare-workers-publish
Deploy static HTML files to Cloudflare Workers with 1Password credential management.