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.
npx skills add RobotFlow-Labs/skills-repo --skill analyzing-tls-certificate-transparency-logsgit clone --depth 1 https://github.com/RobotFlow-Labs/skills-repoWrote 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/skills/robotflow-labs/skills-repo/analyzing-tls-certificate-transparency-logs)<a href="https://agentmods.dev/skills/robotflow-labs/skills-repo/analyzing-tls-certificate-transparency-logs"><img src="https://agentmods.dev/badge/skills/robotflow-labs/skills-repo/analyzing-tls-certificate-transparency-logs/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/skills/robotflow-labs/skills-repo/analyzing-tls-certificate-transparency-logs"><img src="https://agentmods.dev/badge/skills/robotflow-labs/skills-repo/analyzing-tls-certificate-transparency-logs.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.00067 | $0.00359 |
| Opus 5 | $0.00034 | $0.00179 |
| Sonnet 5 | $0.00013 | $0.00072 |
| Haiku 4.5 | $0.00007 | $0.00036 |
Grade A, and why
analyzing-tls-certificate-transparency-logs 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 52 lines · 67 tokens per session scan A 29183850644e
analyzing-tls-certificate-transparency-logs is a skill published in the GitHub repository RobotFlow-Labs/skills-repo (2 stars, last pushed 5mo ago), with no licence file. It adds 67 tokens to every session and 359 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
analyzing-tls-certificate-transparency-logs
Queries Certificate Transparency logs via crt.sh and pycrtsh to detect phishing domains, unauthorized certificate issuance, and shadow IT. Monitors newly issued certificates for typosquatting and brand impersonation using Levenshtein distance. Use for proactive phishing domain detection and certificate monitoring.
analyzing-tls-certificate-transparency-logs
Queries Certificate Transparency logs via crt.sh and pycrtsh to detect phishing domains, unauthorized certificate issuance, and shadow IT. Monitors newly issued certificates for typosquatting and brand impersonation using Levenshtein distance. Use for proactive phishing domain detection and certificate monitoring.
analyzing-tls-certificate-transparency-logs
Queries Certificate Transparency logs via crt.sh and pycrtsh to detect phishing domains, unauthorized certificate issuance, and shadow IT. Monitors newly issued certificates for typosquatting and brand impersonation using Levenshtein distance. Use for proactive phishing domain detection and certificate monitoring.
acme.sh
Use when automating SSL/TLS certificate issuance and renewal from Let's Encrypt, ZeroSSL, or BuyPass — wildcard certs, DNS API mode for 150+ providers, Nginx/Apache auto-reload. acme.sh: pure Shell ACME client, zero dependencies, crontab-friendly auto-renewal.
ssl-tls
TLS certificate lifecycle — Let's Encrypt HTTP-01 and DNS-01 issuance, renewal automation, mTLS, HSTS, OCSP stapling, certificate inspection, and Nginx TLS hardening.
ssl-tls
A guide to SSL/TLS certificates, which help prove a website's identity and encrypt network traffic. It uses OpenSSL to create keys, certificate requests, self-signed certificates, and certificate details.