Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add TLS-Radar/tlsradar-claude-plugin/plugin install tlsradarWrote 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/commands/tls-radar/tlsradar-claude-plugin/tls-cert)<a href="https://agentmods.dev/commands/tls-radar/tlsradar-claude-plugin/tls-cert"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-cert/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/commands/tls-radar/tlsradar-claude-plugin/tls-cert"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-cert.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.00009 | $0.02759 |
| Opus 5 | $0.00005 | $0.01380 |
| Sonnet 5 | $0.00002 | $0.00552 |
| Haiku 4.5 | $0.00001 | $0.00276 |
Grade A, and why
tls-cert 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 8d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue a free SSL/TLS certificate from Let's Encrypt for $ARGUMENTS, entirely through the TLS Radar MCP server's certificate tools. The private key is generated locally and never leaves the machine.
1. Choose the validation (challenge) method
Read ${HOME}/.config/tlsradar/config.json (it may not exist). Its shape:
{ "default_challenge": "dns-01-cloudflare",
"per_domain": { "example.com": "http-01" } }
Pick the method in this order: a per_domain entry for $ARGUMENTS → else default_challenge → else ask the user, offering:
| Method | How it's proven | Best when |
|---|---|---|
dns-01 (manual TXT) |
You show a TXT record; the user adds it by hand | Any domain; no API token |
dns-01-cloudflare |
Claude sets the TXT record via the Cloudflare API ($CLOUDFLARE_API_TOKEN) |
Domain on Cloudflare - fully automated |
dns-01-route53 |
Claude sets the TXT record via the AWS CLI (aws configured) |
Domain on Route 53 - fully automated |
http-01 |
Serve a file on http://$ARGUMENTS port 80 |
You control the web server; issues the apex only (no www) |
When the user picks one, ask "save as the default?" - if yes, write it back to default_challenge (or per_domain["$ARGUMENTS"] if they say "just for this domain"), preserving the rest of the file. Create ~/.config/tlsradar first if needed.
The Beacon challenge value is http-01 for http-01, otherwise dns-01 (all three dns-01 variants differ only in how the plugin sets the TXT record).
2. Start the order (or resume one)
Resume check first: read ${HOME}/.config/tlsradar/orders/$ARGUMENTS.json (it may not exist). If it exists and has an order_id but no completed_at, there's an in-flight order from a previous session - tell the user when it was started (created_at) and offer to resume instead of starting over: skip create_certificate, re-show the saved challenge records if they still need publishing, and continue from step 4 with the saved order_id (passing the saved resume_token at finalize). If resuming fails because the order is gone and can't be rehydrated, or the user declines, start fresh below (the new order overwrites the file).
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.
- 8d ago First seen · 129 lines · 9 tokens per session scan A 02ac6bf5fa67
tls-cert is a command published in the GitHub repository TLS-Radar/tlsradar-claude-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 2,759 once invoked, about $0.0000 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 commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
cloudflare-api
Hit the Cloudflare REST API for bulk, fleet, and operations wrangler can't do.
cloudflare-worker-builder
Scaffold and deploy a Cloudflare Worker with Hono routing.
ops-grafana-dashboard
Creation of Grafana dashboards with automatic provisioning.
tanstack-start
Build a full-stack TanStack Start app on Cloudflare Workers from scratch.
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP.