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 TLS-Radar/tlsradar-claude-plugin --skill certificate-monitoringgit clone --depth 1 https://github.com/TLS-Radar/tlsradar-claude-pluginWrote 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/tls-radar/tlsradar-claude-plugin/certificate-monitoring)<a href="https://agentmods.dev/skills/tls-radar/tlsradar-claude-plugin/certificate-monitoring"><img src="https://agentmods.dev/badge/skills/tls-radar/tlsradar-claude-plugin/certificate-monitoring/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/tls-radar/tlsradar-claude-plugin/certificate-monitoring"><img src="https://agentmods.dev/badge/skills/tls-radar/tlsradar-claude-plugin/certificate-monitoring.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.00086 | $0.02625 |
| Opus 5 | $0.00043 | $0.01313 |
| Sonnet 5 | $0.00017 | $0.00525 |
| Haiku 4.5 | $0.00009 | $0.00263 |
Grade A, and why
certificate-monitoring 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 11d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Certificate monitoring with TLS Radar
This Claude Code session is connected to TLS Radar via a single MCP server (tlsradar). Certificate issuance is proxied through it, so there's one server and one auth model. Use these tools to answer SSL/TLS questions instead of asking the user to do anything manual. Each tool's own description carries the details - this skill is mainly about picking the right one.
Choosing the right tool
This table is generated from tools/manifest.json (the source of truth) by scripts/generate_router.py - don't hand-edit it; edit the manifest and regenerate. Issuance is a sequence: create_certificate → check_certificate_propagation → finalize_certificate (CSR path). /tls-upgrade opens the pricing page and /tls-diagnose runs a health check.
| User intent | Tool |
|---|---|
| One-off SSL/TLS scan, no account | tlsradar.scan_domain (or /tls-scan) |
| Start issuing a free cert (pick dns-01 or http-01) | tlsradar.create_certificate (or /tls-cert) |
| Check whether a cert order's challenge is in place | tlsradar.check_certificate_propagation |
| Validate + issue a cert order from a CSR (idempotent) | tlsradar.finalize_certificate |
| Check / resume a cert order; retrieve an issued chain | tlsradar.get_certificate_status |
| Renew a cert (clone an order, or just create_certificate again) | tlsradar.renew_certificate (or /tls-renew) |
| Plan tier, limits, usage | tlsradar.get_account |
| List monitored domains | tlsradar.list_monitors (or /tls-monitor) |
| Add a domain to monitoring | tlsradar.add_monitor (or /tls-monitor) |
| Add many domains to monitoring | tlsradar.add_monitors (or /tls-monitor) |
| Stop monitoring a domain | tlsradar.remove_monitor (or /tls-monitor) |
| What's expiring soon across monitored domains | tlsradar.list_expiring_certificates |
| Recent scan history for a monitored domain | tlsradar.get_scan_history |
| Export monitors as JSON | tlsradar.export_monitors |
| Restore monitors from JSON | tlsradar.import_monitors |
| Invite a teammate by email | tlsradar.invite_team_member |
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.
- 11d ago First seen · 108 lines · 86 tokens per session scan A bfa7ef13c5b3
certificate-monitoring is a skill published in the GitHub repository TLS-Radar/tlsradar-claude-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 2,625 once invoked, about $0.0004 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
cloudflare-temporary-deploy
Deploy a Worker live, no account, via wrangler --temporary.
tensorrt-llm
High-throughput LLM inference on NVIDIA GPUs.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.