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-upgrade)<a href="https://agentmods.dev/commands/tls-radar/tlsradar-claude-plugin/tls-upgrade"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-upgrade/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-upgrade"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-upgrade.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.00535 |
| Opus 5 | $0.00004 | $0.00267 |
| Sonnet 5 | $0.00002 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
tls-upgrade 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open TLS Radar's pricing page in the user's browser. This is the explicit funnel command - users who want more monitors, Slack alerts, or vulnerability scanning use this to compare and choose.
Behavior
If $ARGUMENTS is a known plan tier (starter, pro, or business), open that tier's page directly:
open 'https://tlsradar.com/pricing?source=plugin&utm_content=cli_upgrade&plan=<tier>'
If $ARGUMENTS is empty or anything else, open the main pricing page:
open 'https://tlsradar.com/pricing?source=plugin&utm_content=cli_upgrade'
After opening, briefly orient the user on the tiers. Do not quote exact prices or feature counts from memory - they change, and stale numbers read as false advertising. If the user is already connected, prefer live values from tlsradar.get_account (but don't trigger an auth prompt just for this). Otherwise keep it general and let the page you just opened carry the current, exact numbers:
- Starter (plans start around $10/mo) - the usual first upgrade: more monitors, more frequent checks, and vulnerability scanning.
- Pro - for larger portfolios: many more monitors and advanced analytics.
- Business - teams and high scale: Slack & webhook alerts, custom schedules, revocation monitoring.
Point the user to the open pricing page for the exact prices, monitor counts, and alert quotas. End with a one-liner about what stays the same on every plan: REST API, Claude Code plugin, and email notifications.
Why this command exists
Most upgrade prompts in the plugin are reactive - when a user hits a limit, the 402 response includes upgrade options. This command is the proactive path: a user who just wants to evaluate plans without hitting an error.
Things this command should NOT do
- Don't try to charge the user or collect payment info - that's the web app's job.
- Don't push a specific tier unless the user named it. Lead with the user's likely next-tier (Starter for free users, Pro for Starter, etc.) but don't insist.
- Don't recite exact prices/quotas from memory - they go stale. Use live
tlsradar.get_accountdata or defer to the pricing page. - Don't run
tlsradar.get_accountif it would prompt for auth - the goal here is friction-free upgrade browsing.
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 · 35 lines · 8 tokens per session scan A 0947b86de467
tls-upgrade 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 535 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
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.