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 LuuOW/meridian-mcp --skill ssl-tlsgit clone --depth 1 https://github.com/LuuOW/meridian-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/luuow/meridian-mcp/ssl-tls)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/ssl-tls"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/ssl-tls/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/luuow/meridian-mcp/ssl-tls"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/ssl-tls.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.01879 |
| Opus 5 | $0.00022 | $0.00940 |
| Sonnet 5 | $0.00009 | $0.00376 |
| Haiku 4.5 | $0.00004 | $0.00188 |
Grade A, and why
ssl-tls scanned grade A with 2 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 6d 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 rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 /etc/letsencrypt/cloudflare.ini Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --cert client.crt --key client.key --cacert ca.crt https://api.internal/health How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ssl-tls
TLS certificate management for production services. Covers Let's Encrypt issuance strategies, Nginx TLS hardening, mutual TLS for internal service auth, and certificate inspection/debugging.
1) Let's Encrypt — HTTP-01 (Single Domain)
apt install certbot python3-certbot-nginx
# Issue cert and auto-configure Nginx
certbot --nginx -d example.com -d www.example.com
# Issue cert only (configure Nginx manually)
certbot certonly --nginx -d example.com
# Standalone mode (if Nginx not installed)
certbot certonly --standalone -d example.com
# Verify auto-renewal timer
systemctl status certbot.timer
certbot renew --dry-run
2) Let's Encrypt — DNS-01 (Wildcard)
pip install certbot-dns-cloudflare
cat > /etc/letsencrypt/cloudflare.ini << 'EOF'
dns_cloudflare_api_token = YOUR_CF_TOKEN
EOF
chmod 600 /etc/letsencrypt/cloudflare.ini
certbot certonly \
--dns-cloudflare \
--dns-cloudflare-credentials /etc/letsencrypt/cloudflare.ini \
-d "*.example.com" -d "example.com"
3) Nginx TLS Hardening
server {
listen 443 ssl http2;
server_name example.com;
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
# Modern compatibility (drops IE11 / old Android)
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256;
ssl_prefer_server_ciphers off;
# Session resumption
ssl_session_timeout 1d;
ssl_session_cache shared:MozSSL:10m;
ssl_session_tickets off;
# OCSP stapling
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/letsencrypt/live/example.com/chain.pem;
resolver 1.1.1.1 8.8.8.8 valid=300s;
resolver_timeout 5s;
# HSTS — preload-ready (6 months)
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload" always;
# Other security headers
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options SAMEORIGIN always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
}
# HTTP → HTTPS redirect
server {
listen 80;
server_name example.com www.example.com;
return 301 https://$host$request_uri;
}
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.
- 6d ago First seen · 200 lines · 43 tokens per session scan A c52003376170
ssl-tls is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,879 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
nginx-docs
NGINX 1.29.x — web server, reverse proxy, load balancing, HTTP/stream/mail modules, SSL, HTTP/2, HTTP/3.
acme.sh
Use when automating SSL/TLS certificate issuance and renewal from Let's Encrypt, ZeroSSL, or BuyPass — wildcard certs, DNS API mode for 150+ providers, Nginx/Apache auto-reload. acme.sh: pure Shell ACME client, zero dependencies, crontab-friendly auto-renewal.
acme
ACME protocol and SSL/TLS certificate automation reference. Covers challenge types (HTTP-01, DNS-01, TLS-ALPN-01), major clients (certbot, acme.sh, lego, Caddy), certificate lifecycle management, Kubernetes cert-manager, Docker/Traefik integration, and security best practices.
performing-ssl-certificate-lifecycle-management
SSL/TLS certificate lifecycle management encompasses the full process of requesting, issuing, deploying, monitoring, renewing, and revoking X.509 certificates. Poor certificate management is a leading.
domains-dns
Use when pointing a domain at a host or fixing broken HTTPS — delegating nameservers, writing A/AAAA/CNAME/ALIAS/MX/TXT/CAA rows, apex vs www, standing up auto-renewing TLS, and cutting nameservers over without downtime. NOT inbox placement or warmup (that is email-deliverability), NOT what runs behind the name (that…
cis-aws-foundations-2.17
Ensure that all expired SSL/TLS certificates stored in AWS IAM are removed.