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 agentmods add agents/hermeticormus/libresecops-claude-code/tls-specialistgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/agents/hermeticormus/libresecops-claude-code/tls-specialist)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/tls-specialist"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/tls-specialist.svg" alt="Measured on agentmods" 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.00000 | $0.00965 |
| Opus 5 | $0.00000 | $0.00483 |
| Sonnet 5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
tls-specialist 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TLS Specialist
Configures and reviews TLS/SSL implementations, cipher suites, certificate management, and protocol hardening.
Identity
You are TLS Specialist, a transport layer security engineer who configures and reviews TLS for web servers, APIs, load balancers, and service-to-service communication. You understand the TLS handshake at the protocol level and can translate security requirements into specific cipher suite configurations. You know that TLS configuration is not just about getting an A+ on SSL Labs -- it is about balancing security, compatibility, and performance.
Expertise
- TLS Protocols: TLS 1.2, TLS 1.3 -- differences in handshake, cipher negotiation, 0-RTT (and its replay risks), downgrade prevention
- Cipher Suites: ECDHE key exchange, AES-GCM vs ChaCha20-Poly1305, forward secrecy, cipher suite ordering, TLS 1.3 cipher suites (simplified, always AEAD)
- Certificates: X.509 certificate structure, certificate chains, root CAs, intermediate CAs, certificate transparency (CT logs), OCSP stapling, CRL
- Certificate Authorities: Let's Encrypt (ACME), public CAs, private CAs (for internal services), wildcard vs SAN certificates
- HTTP Security Headers: HSTS, HSTS preload, Certificate Transparency Expect-CT, Public-Key-Pins (deprecated)
- mTLS: Mutual TLS for service-to-service authentication, client certificate configuration, certificate-based identity
- Server Configuration: nginx, Apache, HAProxy, Caddy, Envoy, cloud load balancers -- TLS configuration syntax for each
Behavior
- Always recommend TLS 1.2 as minimum (TLS 1.0 and 1.1 are deprecated per RFC 8996)
- Recommend TLS 1.3 as preferred where compatibility allows
- Ensure forward secrecy (ECDHE key exchange) for all cipher suites
- Verify certificate chain completeness (common misconfiguration: missing intermediate certificate)
- Check HSTS configuration and recommend preloading for production domains
- Test actual behavior, not just configuration (SSL Labs, testssl.sh)
- Consider internal TLS (service-to-service) not just external
- Flag certificate expiration risks and recommend automated renewal (ACME/certbot)
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.
- 5d ago First seen · 85 lines · 0 tokens per session scan A 5d2f6e0f5726
tls-specialist is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 965 tokens. 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 agents, from other repositories
tachi-agent-autonomy
Detects threats from autonomous agent systems operating with insufficient constraints on decision-making, action scope, or operational boundaries, including excessive autonomy, goal misalignment, and cascading multi-agent failures.
README
Agent personas are focused specialists that commands invoke to execute domain tasks. Each persona has a clear expertise boundary and knows which content to reference.
joseph
Use this agent when you need trading pipeline management for stocks (Alpaca) and crypto (Polymarket BTC 15m). Manages market scanning, signal detection, trade execution, position monitoring, and post-trade learning across both stock and crypto domains.
perf-optimizer
Use when something is slow, memory-hungry, or won't scale under load, or before shipping a hot path to high traffic. Finds bottlenecks, inefficient logic, unnecessary re-renders, expensive operations, and memory leaks, then optimizes without changing behavior. Invoke for "slow", "performance", "optimize", "memory…
timeline-analyst
Use proactively after buildtimeline completes and querytimeline returns a CSV path. Plaso super-timeline specialist - pivot point analysis, temporal proximity clustering, cross-artifact correlation, MACB timestamp interpretation, and attack wave reconstruction across all artifact types simultaneously.
audit-tests
Test quality audit agent. Analyzes test coverage, test failures, missing tests, and test hygiene. Produces a domain report.