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.
git 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/commands/tls-radar/tlsradar-claude-plugin/tls-renew)<a href="https://agentmods.dev/commands/tls-radar/tlsradar-claude-plugin/tls-renew"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-renew/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-renew"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-renew.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.00008 | $0.00544 |
| Opus 5 | $0.00004 | $0.00272 |
| Sonnet 5 | $0.00002 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
tls-renew 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 9d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renew the Let's Encrypt certificate for $ARGUMENTS. Renewal issues a fresh 90-day cert for the same domain; the user's monitoring picks up the new cert on the next scan.
Flow
Check local history first: read ${HOME}/.config/tlsradar/orders/$ARGUMENTS.json (written by /tls-cert; may not exist). If present it carries the previous order's order_id, email, challenge, and created_at/completed_at - use it to skip re-asking: confirm with the user that the saved email and challenge method are still right, then reuse them.
tlsradar.renew_certificate clones an existing order by its order_id, and orders are purged ~24h after creation - so months later at renewal time there's usually no order to clone. Two cases:
- No usable
order_id(the normal case - the saved order is older than ~24h): just run a fresh issuance - it is the renewal. Follow/tls-certexactly:tlsradar.create_certificate(domain=$ARGUMENTS, email=…)→ publish TXT →tlsradar.check_certificate_propagationuntil green → generate a CSR locally (thecert_helper.py csrstep - it backs up the old key automatically) →tlsradar.finalize_certificate(order_id, csr_pem). - The saved (or user-supplied)
order_idis less than ~24h old: calltlsradar.renew_certificatewith it to get a fresh order + new TXT records, then continue from the propagation step as above.
Either way the private key is generated locally (CSR path) and the monitoring handoff fires automatically when the cert completes - you do not register anything.
When to suggest this proactively
If the user runs an expiry check and any entry shows < 30 days remaining, suggest /tls-renew <domain>. Don't auto-renew without asking - renewal involves DNS changes the user controls.
Things this command should NOT do
- Don't renew an unrelated domain just because it's expiring - only act on
$ARGUMENTS. - Don't call
tlsradar.renew_certificatewith a domain - it takes anorder_id. Without one, usetlsradar.create_certificate. - Don't tell the user to manually update monitoring afterward - the cert change is picked up on the next scheduled scan.
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.
- 9d ago First seen · 29 lines · 8 tokens per session scan A 231ea3abcbc1
tls-renew is a command published in the GitHub repository TLS-Radar/tlsradar-claude-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 544 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.