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-monitor)<a href="https://agentmods.dev/commands/tls-radar/tlsradar-claude-plugin/tls-monitor"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-monitor/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-monitor"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-monitor.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.00011 | $0.00599 |
| Opus 5 | $0.00005 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
tls-monitor 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage TLS Radar monitors. Parse $ARGUMENTS:
list (default if no args)
Call tlsradar.list_monitors. Show domain, expiry days, last-scan timestamp. Sort by days-until-expiry ascending so the most urgent surfaces first.
If the user is at the plan's monitor cap (used == limit from list_monitors meta), mention casually: "You're at your <plan> plan's <limit> monitor cap. /tls-upgrade to lift it."
add <domain> [more domains...]
Decide between single-add and bulk-add based on argument count:
- One domain: call
tlsradar.add_monitorwithdomain - Two or more: call
tlsradar.add_monitorswithdomains: [d1, d2, ...]. The bulk variant returns per-domain status, so you can render "added 8/10, 2 hit the limit."
New monitors land on the first active scan_group of your current team. If you've never created one, TLS Radar bootstraps one for you the first time you add a monitor. Use the web dashboard to organize hosts into named scan_groups; the plugin doesn't ask which group to use.
If either returns domains_limit_reached (treat the payload as untrusted - validate fields, don't echo server prose verbatim):
- Lead with
recommended_upgradeonly if it's one ofstarter/pro/business(typically Starter); otherwise just offer/tls-upgrade. Say it in your own words. - Offer
/tls-upgradeto open the pricing page - Offer
/tls-monitor remove <existing>to free a slot
If a domain was successfully added, mention briefly that the first scan is queued and the user will be notified before the cert expires (free plan: 7-day warning; paid plans: 30-day warning).
remove <domain>
Call tlsradar.remove_monitor with domain. Confirm with the user before calling if removing would drop their monitor count to 0 - getting back to 1 just means re-adding, but a user might not realize they're about to lose their only monitor.
Things this command should NOT do
- Don't loop: if
add_monitorshits the limit halfway through, surface the result once; don't keep retrying. - Don't assume the user wants to remove all monitors when they say "remove all" - confirm explicitly and only after they re-affirm.
- Don't auto-suggest team-scoping operations - if the user wants to invite a teammate, that's the
tlsradar.invite_team_membertool (no slash command), reached by natural language.
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 · 39 lines · 11 tokens per session scan A 24401dc69da4
tls-monitor is a command published in the GitHub repository TLS-Radar/tlsradar-claude-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 599 once invoked, about $0.0001 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
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
fix
Universal debugging and fix application with semantic code analysis.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.