Agent skill

mTLS Configuration

Walks through mutual TLS between services in a zero-trust setup: certificate hierarchy, rotation, a gradual PERMISSIVE-to-STRICT rollout and handshake debugging.

MITAuto-check passedSecurity

Install mTLS Configuration

skills CLI

$ npx skills add wshobson/agents --skill mtls-configuration -a claude-code

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

GitHub CLI

$ gh skill install wshobson/agents mtls-configuration --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/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/cloud-infrastructure/skills/mtls-configuration .claude/skills/mtls-configuration && 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/

Paste into Claude Code

Install the "mtls-configuration" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cloud-infrastructure/skills/mtls-configuration into .claude/skills/mtls-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mtls-configuration", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/wshobson/agents/tree/main/plugins/cloud-infrastructure/skills/mtls-configuration

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add wshobson/agents --skill mtls-configuration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install wshobson/agents mtls-configuration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/cloud-infrastructure/skills/mtls-configuration .agents/skills/mtls-configuration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "mtls-configuration" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cloud-infrastructure/skills/mtls-configuration into .agents/skills/mtls-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mtls-configuration", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add wshobson/agents --skill mtls-configuration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install wshobson/agents mtls-configuration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/cloud-infrastructure/skills/mtls-configuration .cursor/skills/mtls-configuration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "mtls-configuration" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cloud-infrastructure/skills/mtls-configuration into .cursor/skills/mtls-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mtls-configuration", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/wshobson/agents.git --path plugins/cloud-infrastructure/skills/mtls-configuration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add wshobson/agents --skill mtls-configuration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install wshobson/agents mtls-configuration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/cloud-infrastructure/skills/mtls-configuration .gemini/skills/mtls-configuration && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "mtls-configuration" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cloud-infrastructure/skills/mtls-configuration into .gemini/skills/mtls-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mtls-configuration", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install wshobson/agents mtls-configuration

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add wshobson/agents --skill mtls-configuration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/cloud-infrastructure/skills/mtls-configuration .github/skills/mtls-configuration && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "mtls-configuration" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cloud-infrastructure/skills/mtls-configuration into .github/skills/mtls-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mtls-configuration", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add wshobson/agents --skill mtls-configuration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install wshobson/agents mtls-configuration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/cloud-infrastructure/skills/mtls-configuration .opencode/skills/mtls-configuration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "mtls-configuration" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cloud-infrastructure/skills/mtls-configuration into .opencode/skills/mtls-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mtls-configuration", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: mtls-configuration
GitHub stars: 40k
Used in: 9 other repos
Token cost: ~588 tokens
SKILL.md length: 138 words
Files: 2 (incl. references)
Skills in repo: 142
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Walks through mutual TLS between services in a zero-trust setup: certificate hierarchy, rotation, a gradual PERMISSIVE-to-STRICT rollout and handshake debugging.

Works in 2 steps: mTLS Flow → Certificate Hierarchy
Enforcing mutual TLS between services in a service mesh
SKILL.md covers When to Use This Skill, Core Concepts, Templates and detailed worked… and Best Practices
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill is a reference for mutual TLS in a service mesh, where both sides of a connection present certificates. It sketches the handshake between two services and a certificate hierarchy that runs from a long-lived self-signed root CA down to cluster-level intermediate CAs.

Operating advice includes starting in PERMISSIVE mode and moving to STRICT, keeping workload certificates short-lived, automating rotation, alerting on expiry, logging TLS errors and verifying the full chain. Typical triggers are compliance requirements such as PCI-DSS and HIPAA, and multi-cluster setups. Templates are kept in references/details.md.

When your agent uses it

Enforcing mutual TLS between services in a service mesh
Setting up certificate rotation for workload identities
Debugging failed TLS handshakes between internal services
Preparing service-to-service encryption for PCI-DSS or HIPAA

Example prompts

“Move our mesh from PERMISSIVE to STRICT mTLS without breaking existing traffic.”
“Design a certificate hierarchy with a root CA and one intermediate per cluster.”
“The handshake between the billing and orders services fails. Check the certificate chain.”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

mTLS Flow
Certificate Hierarchy

What it can do on your machine

Read from SKILL.md and the folder at commit 46891e7. 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
No scripts in the folder and no shell commands in SKILL.md.
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

mTLS Configuration loads about 588 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 138 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 138 words, ~588 tokens.

Download SKILL.mdSave it as .claude/skills/mtls-configuration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: mtls-configuration
description: Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.

mTLS Configuration

Comprehensive guide to implementing mutual TLS for zero-trust service mesh communication.

When to Use This Skill

Implementing zero-trust networking
Securing service-to-service communication
Certificate rotation and management
Debugging TLS handshake issues
Compliance requirements (PCI-DSS, HIPAA)
Multi-cluster secure communication

Core Concepts

1. mTLS Flow

┌─────────┐                              ┌─────────┐
│ Service │                              │ Service │
│    A    │                              │    B    │
└────┬────┘                              └────┬────┘
     │                                        │
┌────┴────┐      TLS Handshake          ┌────┴────┐
│  Proxy  │◄───────────────────────────►│  Proxy  │
│(Sidecar)│  1. ClientHello             │(Sidecar)│
│         │  2. ServerHello + Cert      │         │
│         │  3. Client Cert             │         │
│         │  4. Verify Both Certs       │         │
│         │  5. Encrypted Channel       │         │
└─────────┘                              └─────────┘

2. Certificate Hierarchy

Root CA (Self-signed, long-lived)
    │
    ├── Intermediate CA (Cluster-level)
    │       │
    │       ├── Workload Cert (Service A)
    │       └── Workload Cert (Service B)
    │
    └── Intermediate CA (Multi-cluster)
            │
            └── Cross-cluster certs

Templates and detailed worked examples

Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.

Best Practices

Do's

Start with PERMISSIVE - Migrate gradually to STRICT
Monitor certificate expiry - Set up alerts
Use short-lived certs - 24h or less for workloads
Rotate CA periodically - Plan for CA rotation
Log TLS errors - For debugging and audit

Don'ts

Don't disable mTLS - For convenience in production
Don't ignore cert expiry - Automate rotation
Don't use self-signed certs - Use proper CA hierarchy
Don't skip verification - Verify the full chain

Files

SKILL.md and 1 other file (references) in plugins/cloud-infrastructure/skills/mtls-configuration of wshobson/agents.

SKILL.md
references/details.md

Open the folder on GitHubat commit 46891e7

Used in 9 other repositories

We found 19 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 9 other GitHub owners. This page covers the copy in wshobson/agents, which our catalogue first saw on October 7, 2026.

Compare with similar skills

mTLS Configuration 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.

mTLS Configuration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
mTLS Configuration this skillwshobson/agents	40k	9 repos	~588	Automated safety check: Pass	MIT	4 days ago
Azure Firewallvinayaklatthe/microsoft-security-skills	175	—	~1.7k	Automated safety check: Pass	MIT	3 mo ago
Performing Ot Network Security Assessmentmukul975/Anthropic-Cybersecurity-Skills	34k	—	~6.1k	Automated safety check: Pass	Apache-2.0	1 mo ago
Network Engineeringaiskillstore/marketplace	430	1 repos	~1.4k	Automated safety check: Pass	None	today
Nmap Network Scanautomateyournetwork/netclaw	676	—	~1.3k	Automated safety check: Pass	Apache-2.0	3 days ago
Kubernetes Network Security Auditkubeshark/kubeshark	12k	—	~7.3k	Automated safety check: Notes	Apache-2.0	yesterday

Similar skills

Azure Firewall
vinayaklatthe/microsoft-security-skills
Guidance for Azure Firewall — managed cloud-native L3-L7 stateful network firewall for centralised egress, east-west, and ingress control.
175 GitHub stars~1.7k tokensUpdated 3 mo ago
SecurityAuto-check passed
Performing Ot Network Security Assessment
mukul975/Anthropic-Cybersecurity-Skills
This skill covers conducting comprehensive security assessments of Operational Technology (OT) networks including SCADA systems, DCS architectures, and industrial control system communication paths.
34k GitHub stars~6.1k tokensUpdated 1 mo ago
SecurityAuto-check passed
Network Engineering
aiskillstore/marketplace
Network architecture, troubleshooting, and infrastructure patterns.
430 GitHub starsUsed in 1 repo~1.4k tokens
DevOps & CloudAuto-check passed
Nmap Network Scan
automateyournetwork/netclaw
Host discovery and port scanning using nmap — ICMP/ARP host discovery, SYN/TCP/UDP port scanning with scope enforcement and audit logging.
676 GitHub stars~1.3k tokensUpdated 3 days ago
SecurityAuto-check passed
Kubernetes Network Security Audit
kubeshark/kubeshark
Hunts for compromised workloads and malicious traffic in a Kubernetes cluster by sweeping network data through Kubeshark MCP, mapped to MITRE ATT&CK.
12k GitHub stars~7.3k tokensUpdated yesterday
SecurityAuto-check: notes
Firewall Config
sickn33/agentic-awesome-skills
Configure iptables, nftables, and cloud firewalls. An agent skill from sickn33/agentic-awesome-skills.
47k GitHub starsUsed in 2 repos~3.2k tokens
SecurityAuto-check: notes

Questions about mTLS Configuration

What does mTLS Configuration do?

Walks through mutual TLS between services in a zero-trust setup: certificate hierarchy, rotation, a gradual PERMISSIVE-to-STRICT rollout and handshake debugging. The skill is a reference for mutual TLS in a service mesh, where both sides of a connection present certificates. It sketches the handshake between two services and a certificate hierarchy that runs from a long-lived self-signed root CA down to cluster-level intermediate CAs.

When should I use mTLS Configuration?

mTLS Configuration fits situations like: enforcing mutual TLS between services in a service mesh; setting up certificate rotation for workload identities; debugging failed TLS handshakes between internal services; preparing service-to-service encryption for PCI-DSS or HIPAA.

How do I install mTLS Configuration in Claude Code?

Run `npx skills add wshobson/agents --skill mtls-configuration -a claude-code`. Or copy the skill folder (plugins/cloud-infrastructure/skills/mtls-configuration in wshobson/agents) into .claude/skills/mtls-configuration in your project. Claude Code loads it when a task matches its description.

How do I install mTLS Configuration in Codex?

Run `npx skills add wshobson/agents --skill mtls-configuration -a codex`. Or copy the skill folder (plugins/cloud-infrastructure/skills/mtls-configuration in wshobson/agents) into .agents/skills/mtls-configuration in your project. Codex loads it when a task matches its description.

Can I use mTLS Configuration 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 wshobson/agents --skill mtls-configuration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mtls-configuration, .gemini/skills/mtls-configuration, .github/skills/mtls-configuration and .opencode/skills/mtls-configuration in your project.

What does mTLS Configuration need to run?

SKILL.md names no scripts, command-line tools or credentials: mTLS Configuration is instructions for the agent only.

Does mTLS Configuration 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 mTLS Configuration 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. Review the folder before installing.

What licence does mTLS Configuration use?

mTLS Configuration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does mTLS Configuration use?

About 588 tokens (SKILL.md is roughly 2.4k 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.5k tokens, read only when the agent opens those files.

What are the alternatives to mTLS Configuration?

Skills that share tags, products or a category with mTLS Configuration: Azure Firewall (vinayaklatthe/microsoft-security-skills, 175 stars), Performing Ot Network Security Assessment (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Network Engineering (aiskillstore/marketplace, 430 stars) and Nmap Network Scan (automateyournetwork/netclaw, 676 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains mTLS Configuration?

wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,305 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.

Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install mTLS Configuration

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

mTLS Configuration

When to Use This Skill

Core Concepts

1. mTLS Flow

2. Certificate Hierarchy

Templates and detailed worked examples

Best Practices

Do's

Don'ts

Files

Used in 9 other repositories

Compare with similar skills

Similar skills

More from wshobson/agents

Related

Questions about mTLS Configuration