Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -278,1 +278,0 @@
-<summary>Session issues</summary> - Browser profile is stored at `~/.linkedin-mcp/profile/` - Managed browser downloads are cached at `~/.linkedin-mcp/patchrigh
@@ -287,1 +286,0 @@
-<summary>Login issues</summary> - Make sure you have only one active LinkedIn session at a time - LinkedIn may require a login confirmation in the LinkedIn mobi
@@ -306,1 +304,0 @@
-<summary>Told to run <code>--login</code> on the host when you already did</summary> - If tool calls answer "No valid LinkedIn session is available in Docker" o
@@ -359,1 +356,0 @@
-<summary>Login issues</summary> - Make sure you have only one active LinkedIn session at a time - LinkedIn may require a login confirmation in the LinkedIn mobi
@@ -378,1 +374,0 @@
-<summary>Use your own Chrome</summary> - Set **Chrome executable** in the extension's settings to a Chrome, Chromium or Chrome for Testing binary, such as `/usr
@@ -386,1 +381,0 @@
-<summary>Told to run <code>--login</code> on the host when you already did</summary> - If tool calls answer "No valid LinkedIn session is available in Docker" o
diff --git a/AGENTS.md b/AGENTS.md
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -276,1 +276,0 @@
-treats every converted secret as required. The three optional proxy credentials
diff --git a/tests/test_bootstrap.py b/tests/test_bootstrap.py
--- a/tests/test_bootstrap.py
+++ b/tests/test_bootstrap.py
@@ -3754,1 +3754,0 @@
-b"sitecustomize: https://user:[email protected]/x?token=secret\x1b[2J\n"
@@ -3833,1 +3832,0 @@
-"sitecustomize: https://ci-bot:[email protected]/p?key=s3cr3t working\n"
@@ -4911,1 +4909,0 @@
-url = "https://ci-bot:[email protected]/chromium.zip"
@@ -5647,1 +5644,0 @@
-"https://ci-bot:[email protected]/x.zip",
@@ -5653,1 +5649,0 @@
-"https://ci-bot:s3cr3t@[email protected]/x.zip",
diff --git a/.github/mcp/server.json b/.github/mcp/server.json
--- a/.github/mcp/server.json
+++ b/.github/mcp/server.json
@@ -31,1 +31,0 @@
-…e://host:port (http, https, socks4 or socks5). May also include credentials, as http://user:password@host:port. Only browser traffic is routed.", "isSecret": true …
@@ -75,1 +74,0 @@
-…e://host:port (http, https, socks4 or socks5). May also include credentials, as http://user:password@host:port. Only browser traffic is routed.", "isSecret": true …
diff --git a/manifest.json b/manifest.json
--- a/manifest.json
+++ b/manifest.json
@@ -163,1 +163,0 @@
-…e://host:port (http, https, socks4 or socks5). May also include credentials, as http://user:password@host:port. Only browser traffic is routed.", "required": false, "def…
diff --git a/tests/test_config.py b/tests/test_config.py
--- a/tests/test_config.py
+++ b/tests/test_config.py
@@ -1014,1 +1014,0 @@
-config = BrowserConfig(proxy_server=f"http://user:{self.SECRET}@gate:7000")
@@ -1024,1 +1023,0 @@
-config = BrowserConfig(proxy_server="http://user:p%40ss@gate:7000")
@@ -1048,1 +1046,0 @@
-"proxy_server": "http://u:p@host:8080",
@@ -1113,1 +1110,0 @@
-monkeypatch.setenv("PROXY_SERVER", f"http://envuser:{self.SECRET}@gate:7000")
@@ -1155,1 +1151,0 @@
-AppConfig(), ["--proxy-server", f"http://u:{self.SECRET}@h:8080"]
@@ -1295,1 +1290,0 @@
-"""A username with an empty password is a legitimate proxy credential.
diff --git a/tests/test_pr_title.py b/tests/test_pr_title.py
--- a/tests/test_pr_title.py
+++ b/tests/test_pr_title.py
@@ -157,1 +157,0 @@
-"",
@@ -168,1 +167,0 @@
-"fix: ​",
@@ -169,1 +167,0 @@
-"fix(​): Subject",
@@ -170,1 +167,0 @@
-"fix: Subject.​",
@@ -180,1 +176,0 @@
-"fix: ​",
diff --git a/tests/test_tools.py b/tests/test_tools.py
--- a/tests/test_tools.py
+++ b/tests/test_tools.py
@@ -485,1 +485,0 @@
-shaped = ToolError("Proxy refused http://acctzone9:[email protected]:7000")
diff --git a/scripts/login-viewer.html b/scripts/login-viewer.html
--- a/scripts/login-viewer.html
+++ b/scripts/login-viewer.html
@@ -2,1 +2,0 @@
-The Docker login viewer's page, served by websockify from /usr/share/novnc next to Debian's noVNC, whose documented RFB API it uses. login_viewer.py prints its 
diff --git a/tests/test_throttle.py b/tests/test_throttle.py
--- a/tests/test_throttle.py
+++ b/tests/test_throttle.py
@@ -326,1 +326,0 @@
-RuntimeError(f"failed via http://{user}:{secret}@gate.example:7000"),

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 4.30.0. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: linkedin-mcp-server: Collapsed <details> block carrying instructions (KillerSkills verdict caution 69)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 69/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/docker/linkedin-mcp-server/4.30.0

## Findings with a location
- `README.md:278` · Collapsed <details> block carrying instructions — README.md:278 · Collapsed <details> block carrying instructions
- `AGENTS.md:276` · Credential pass-through configuration — AGENTS.md:276 · Credential pass-through configuration — agent relays sensitive credentials
- `README.md:306` · Collapsed <details> block carrying instructions — README.md:306 · Collapsed <details> block carrying instructions
- `README.md:386` · Collapsed <details> block carrying instructions — README.md:386 · Collapsed <details> block carrying instructions
- `tests/test_bootstrap.py:5653` · URL with embedded credentials — tests/test_bootstrap.py:5653 · URL with embedded credentials — may be phishing or credential leaking
- `README.md:378` · Collapsed <details> block carrying instructions — README.md:378 · Collapsed <details> block carrying instructions
- `.github/mcp/server.json:75` · URL with embedded credentials — .github/mcp/server.json:75 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_bootstrap.py:3754` · URL with embedded credentials — tests/test_bootstrap.py:3754 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_bootstrap.py:5647` · URL with embedded credentials — tests/test_bootstrap.py:5647 · URL with embedded credentials — may be phishing or credential leaking
- `.github/mcp/server.json:31` · URL with embedded credentials — .github/mcp/server.json:31 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_bootstrap.py:4911` · URL with embedded credentials — tests/test_bootstrap.py:4911 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_bootstrap.py:3833` · URL with embedded credentials — tests/test_bootstrap.py:3833 · URL with embedded credentials — may be phishing or credential leaking

## Proposed change
The attached patch removes the 29 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._