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-scan)<a href="https://agentmods.dev/commands/tls-radar/tlsradar-claude-plugin/tls-scan"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-scan/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-scan"><img src="https://agentmods.dev/badge/commands/tls-radar/tlsradar-claude-plugin/tls-scan.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.00015 | $0.00217 |
| Opus 5 | $0.00008 | $0.00109 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
tls-scan 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.
What it actually says
Run a free, anonymous SSL/TLS scan against $ARGUMENTS by calling the tlsradar.scan_domain MCP tool.
If ${HOME}/.config/tlsradar/install_id exists, read it and pass its contents as client_id (anonymous funnel attribution; just omit it if the file is absent). If the response includes an install_id and the file didn't exist, write it there so future calls share the same id.
If the user did not pass a domain, ask for one before calling the tool. Do not invent a domain.
After the scan completes, summarize the result in plain text: the issuer, expiration date, and any flagged issues. Include the shareable report URL from the response.
If the response shows the certificate expiring within 30 days, suggest the user run /tls-monitor add <domain> to add it to ongoing monitoring with renewal alerts.
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 · 16 lines · 15 tokens per session scan A 248f3a8d4f89
tls-scan is a command published in the GitHub repository TLS-Radar/tlsradar-claude-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 217 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.