Agent skill

Configuring Tls 1 3 For Secure Communications

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and key-exchange group selection, and validates the resulting configuration with openssl sclient and testssl.sh.

Apache-2.0Auto-check passedSecurity

Install Configuring Tls 1 3 For Secure Communications

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill configuring-tls-1-3-for-secure-communications -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills configuring-tls-1-3-for-secure-communications --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/configuring-tls-1-3-for-secure-communications .claude/skills/configuring-tls-1-3-for-secure-communications && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
configuring-tls-1-3-for-secure-communications
GitHub stars
34k
Token cost
~1.1k tokens
SKILL.md length
459 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and key-exchange group selection, and validates the resulting configuration with openssl sclient and testssl.sh.

  • Works in 8 steps: Verify OpenSSL version supports TLS 1.3… → Generate or obtain TLS certificate and… → Configure server to use TLS 1.3 cipher… → …
  • Hardening TLS 1.3 for secure communications
  • SKILL.md covers Overview, When to Use, Prerequisites and Objectives, plus 4 more sections
  • Runs Python scripts from its folder

What it does

Configuring Tls 1 3 For Secure Communications is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and key-exchange group selection, and validates the resulting configuration with openssl sclient and testssl.sh. Use when deploying or hardening TLS 1.3 for secure communications, or when testing a server for common TLS misconfigurations and vulnerabilities.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/api-reference.md` and `references/standards.md`).

It sits in Security, covering Cryptography. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Hardening TLS 1.3 for secure communications
  • Testing a server for common TLS misconfigurations and vulnerabilities

Example prompts

  • “Use the configuring-tls-1-3-for-secure-communications skill to configure TLS 1.3 (RFC 8446) on servers, covering cipher suite and key-exchange group…”
  • “/configuring-tls-1-3-for-secure-communications”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Verify OpenSSL version supports TLS 1.3 (1.1.1+)
  2. Generate or obtain TLS certificate and private key
  3. Configure server to use TLS 1.3 cipher suites
  4. Disable TLS 1.0 and 1.1 (optionally keep 1.2 for compatibility)
  5. Set preferred key exchange groups
  6. Enable OCSP stapling for certificate validation
  7. Test configuration with openssl s_client and testssl.sh
  8. Configure HSTS header for HTTP Strict Transport Security

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Configuring Tls 1 3 For Secure Communications loads about 1.1k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 459 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 459 words, ~1,085 tokens.

Download SKILL.mdSave it as .claude/skills/configuring-tls-1-3-for-secure-communications/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
configuring-tls-1-3-for-secure-communications
description
Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and key-exchange group selection, and validates the resulting configuration with openssl s_client and testssl.sh. Use when deploying or hardening TLS 1.3 for secure communications, or when testing a server for common TLS misconfigurations and vulnerabilities.
domain
cybersecurity
subdomain
cryptography
tags
cryptography, tls, ssl, transport-security, network-security
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
PR.DS-01, PR.DS-02, PR.DS-10
mitre_attack
T1557, T1040, T1573.002, T1539, T1556.004

Configuring TLS 1.3 for Secure Communications

Overview

TLS 1.3 (RFC 8446) is the latest version of the Transport Layer Security protocol, providing significant improvements over TLS 1.2 in both security and performance. It reduces handshake latency to 1-RTT (and 0-RTT for resumed sessions), removes obsolete cipher suites, and mandates perfect forward secrecy. This skill covers configuring TLS 1.3 on servers, validating configurations, and testing for common misconfigurations.

When to Use

  • When deploying or configuring configuring tls 1 3 for secure communications capabilities in your environment
  • When establishing security controls aligned to compliance requirements
  • When building or improving security architecture for this domain
  • When conducting security assessments that require this implementation

Prerequisites

  • Familiarity with cryptography concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Objectives

  • Configure TLS 1.3 on nginx and Apache web servers
  • Implement TLS 1.3 in Python applications using the ssl module
  • Validate TLS configurations with openssl and testssl.sh
  • Understand TLS 1.3 cipher suites and key exchange mechanisms
  • Configure 0-RTT early data with appropriate protections
  • Disable legacy TLS versions (1.0, 1.1) and weak cipher suites

Key Concepts

TLS 1.3 Cipher Suites
Cipher SuiteKey ExchangeAuthenticationEncryptionHash
TLS_AES_256_GCM_SHA384ECDHE/DHECertificateAES-256-GCMSHA-384
TLS_AES_128_GCM_SHA256ECDHE/DHECertificateAES-128-GCMSHA-256
TLS_CHACHA20_POLY1305_SHA256ECDHE/DHECertificateChaCha20-Poly1305SHA-256
TLS 1.3 vs 1.2 Improvements
  • 1-RTT Handshake: Full handshake completes in one round trip (vs 2 in TLS 1.2)
  • 0-RTT Resumption: Resumed connections can send data immediately
  • No RSA Key Exchange: Only ephemeral Diffie-Hellman (mandatory PFS)
  • Simplified Cipher Suites: Removed CBC, RC4, 3DES, static RSA, SHA-1
  • Encrypted Handshake: Server certificate is encrypted after ServerHello
Show full SKILL.md (185 more words)Show less
Key Exchange Groups
  • x25519: Curve25519 ECDH (preferred, fast)
  • secp256r1: NIST P-256 ECDH (widely supported)
  • secp384r1: NIST P-384 ECDH (higher security margin)
  • x448: Curve448 ECDH (highest security)

Workflow

  1. Verify OpenSSL version supports TLS 1.3 (1.1.1+)
  2. Generate or obtain TLS certificate and private key
  3. Configure server to use TLS 1.3 cipher suites
  4. Disable TLS 1.0 and 1.1 (optionally keep 1.2 for compatibility)
  5. Set preferred key exchange groups
  6. Enable OCSP stapling for certificate validation
  7. Test configuration with openssl s_client and testssl.sh
  8. Configure HSTS header for HTTP Strict Transport Security

Security Considerations

  • 0-RTT data is vulnerable to replay attacks; limit to idempotent requests
  • Always include TLS 1.2 fallback if legacy client support is required
  • Use ECDSA certificates for better performance (vs RSA)
  • Enable OCSP stapling to improve client certificate validation
  • Set HSTS header with long max-age and includeSubDomains
  • Monitor for certificate transparency logs

Validation Criteria

  • TLS 1.3 handshake completes successfully
  • Only approved cipher suites are offered
  • Perfect forward secrecy is enforced
  • TLS 1.0 and 1.1 are rejected
  • OCSP stapling is functional
  • Certificate chain is valid and complete
  • testssl.sh reports no vulnerabilities

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references, assets) in skills/configuring-tls-1-3-for-secure-communications of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • assets/template.md
  • references/api-reference.md
  • references/standards.md
  • references/workflows.md
  • scripts/agent.py
  • scripts/process.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Configuring Tls 1 3 For Secure Communications next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Configuring Tls 1 3 For Secure Communications compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Configuring Tls 1 3 For Secure Communications this skillmukul975/Anthropic-Cybersecurity-Skills34k—~1.1kAutomated safety check: PassApache-2.0
Bom Explorecdxgen/cdxgen1.1k—~1.2kAutomated safety check: PassApache-2.0
Crypto Analysishypnguyen1209/offensive-claude388—~2.2kAutomated safety check: PassMIT
Security Reviewvalory-xyz/open-autonomy129—~11kAutomated safety check: NotesApache-2.0
Hashcat Password Recovery WorkflowAgentSecOps/SecOpsAgentKit2201 repos~3.3kAutomated safety check: NotesCustom licence
Altllm Portal Authinternet-court/internet-court-skill6.6k1 repos~632Automated safety check: PassISC

Similar skills

  • Bom Explore

    cdxgen/cdxgen

    Explores and triages a CycloneDX BOM interactively with the cdxi REPL, using built-in commands for dependency trees, licenses, services, cryptographic assets, audit findings, evidence occurrences…

    1.1k GitHub stars~1.2k tokensUpdated today
    SecurityAuto-check passed
  • Crypto Analysis

    hypnguyen1209/offensive-claude

    A skill your agent uses when assessing cryptography — TLS/PKI auditing, RSA/ECC key attacks, ECDSA nonce lattice recovery, symmetric/AEAD misuse, JWT/JOSE forgery, hash cracking, post-quantum…

    388 GitHub stars~2.2k tokensUpdated 13 days ago
    SecurityAuto-check passed
  • Security Review

    valory-xyz/open-autonomy

    Security review of an open-autonomy agent service — cryptographic key handling, dynamic code execution, ABCI authentication and replay, secret exposure, dependency supply chain, and deployment…

    129 GitHub stars~11k tokensUpdated 27 days ago
    SecurityAuto-check: notes
  • Hashcat Password Recovery Workflow

    AgentSecOps/SecOpsAgentKit

    Guides authorized password-hash recovery with hashcat for security audits, forensic cases and policy testing, starting with an explicit authorization check before any cracking runs.

    220 GitHub starsUsed in 1 repo~3.3k tokens
    SecurityAuto-check: notes
  • Altllm Portal Auth

    internet-court/internet-court-skill

    A skill your agent uses when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login…

    6.6k GitHub starsUsed in 1 repo~632 tokens
    SecurityAuto-check passed
  • Webcrypt MCP

    putervision/state-memory-mcp

    Teaches the agent to use the WebCrypt MCP server for AES-256-GCM symmetric encryption, RSA-4096 hybrid encryption, key generation, digital signatures, hashing, and post-quantum cryptography.

    50 GitHub stars~847 tokensUpdated 8 days ago
    SecurityAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Configuring Tls 1 3 For Secure Communications

What does Configuring Tls 1 3 For Secure Communications do?

Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and key-exchange group selection, and validates the resulting configuration with openssl sclient and testssl.sh. Configuring Tls 1 3 For Secure Communications is an agent skill from mukul975/Anthropic-Cybersecurity-Skills.sh.

When should I use Configuring Tls 1 3 For Secure Communications?

Configuring Tls 1 3 For Secure Communications fits situations like: hardening TLS 1.3 for secure communications; testing a server for common TLS misconfigurations and vulnerabilities.

How do I install Configuring Tls 1 3 For Secure Communications in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill configuring-tls-1-3-for-secure-communications -a claude-code`. Or copy the skill folder (skills/configuring-tls-1-3-for-secure-communications in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/configuring-tls-1-3-for-secure-communications in your project. Claude Code loads it when a task matches its description.

How do I install Configuring Tls 1 3 For Secure Communications in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill configuring-tls-1-3-for-secure-communications -a codex`. Or copy the skill folder (skills/configuring-tls-1-3-for-secure-communications in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/configuring-tls-1-3-for-secure-communications in your project. Codex loads it when a task matches its description.

Can I use Configuring Tls 1 3 For Secure Communications in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill configuring-tls-1-3-for-secure-communications -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/configuring-tls-1-3-for-secure-communications, .gemini/skills/configuring-tls-1-3-for-secure-communications, .github/skills/configuring-tls-1-3-for-secure-communications and .opencode/skills/configuring-tls-1-3-for-secure-communications in your project.

What does Configuring Tls 1 3 For Secure Communications need to run?

Going by SKILL.md and its folder, Configuring Tls 1 3 For Secure Communications needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Configuring Tls 1 3 For Secure Communications access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Configuring Tls 1 3 For Secure Communications safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Configuring Tls 1 3 For Secure Communications use?

Configuring Tls 1 3 For Secure Communications is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Configuring Tls 1 3 For Secure Communications use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Configuring Tls 1 3 For Secure Communications?

Skills that share tags, products or a category with Configuring Tls 1 3 For Secure Communications: Bom Explore (cdxgen/cdxgen, 1.1k stars), Crypto Analysis (hypnguyen1209/offensive-claude, 388 stars), Security Review (valory-xyz/open-autonomy, 129 stars) and Hashcat Password Recovery Workflow (AgentSecOps/SecOpsAgentKit, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Configuring Tls 1 3 For Secure Communications?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.