Agent Plugins Marketplace
← All plugins

chrome-not-secure-tls-interception

v1.0.0

Diagnose Chrome's "Your connection to this site is not secure" on a major site (gmail.com, google.com, github.com) on a machine behind a corporate TLS-inspecting proxy (Zscaler, Netskope, Palo Alto, Blue Coat). Use when: (1) Chrome's site-info bubble shows the red triangle and "You should not enter any sensitive information on this site", (2) a CLI `openssl`/`curl` check of the same host looks perfectly clean and you cannot reproduce the browser's complaint, (3) you are about to tell someone their proxy is MITM-ing them. Covers the PAC-proxy blind spot in CLI checks, how to read the intercepted chain, and — critically — why a forged proxy certificate with zero SCTs is the NORMAL steady state and usually NOT the cause.

Claude Code

By voitta-aiLicense: MIT3 GitHub starsUpdated 2 hours ago

Directory evidence

Runtimes
Claude Code
Parsed components
0 skill or MCP entries
Source updated
Sep 28, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install chrome-not-secure-tls-interception for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install chrome-not-secure-tls-interception@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/voitta-ai/skillz

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/chrome-not-secure-tls-interception/.

Plugin files

plugins/chrome-not-secure-tls-interception/
└── .claude-plugin/plugin.json

Plugin manifests1

plugins/chrome-not-secure-tls-interception/.claude-plugin/plugin.json
{
  "name": "chrome-not-secure-tls-interception",
  "description": "Diagnose Chrome's \"Your connection to this site is not secure\" on a major site (gmail.com, google.com, github.com) on a machine behind a corporate TLS-inspecting proxy (Zscaler, Netskope, Palo Alto, Blue Coat). Use when: (1) Chrome's site-info bubble shows the red triangle and \"You should not enter any sensitive information on this site\", (2) a CLI `openssl`/`curl` check of the same host looks perfectly clean and you cannot reproduce the browser's complaint, (3) you are about to tell someone their proxy is MITM-ing them. Covers the PAC-proxy blind spot in CLI checks, how to read the intercepted chain, and — critically — why a forged proxy certificate with zero SCTs is the NORMAL steady state and usually NOT the cause.",
  "version": "1.0.0",
  "author": {
    "name": "voitta-ai"
  },
  "homepage": "https://github.com/voitta-ai/skillz",
  "repository": "https://github.com/voitta-ai/skillz",
  "license": "MIT",
  "skills": "./skills/"
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[chrome-not-secure-tls-interception on Agent Plugins Marketplace](https://pluginsmp.com/plugins/chrome-not-secure-tls-interception)