Propose a patch

Evidence

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

diff --git a/tests/test_cov_100c.py b/tests/test_cov_100c.py
--- a/tests/test_cov_100c.py
+++ b/tests/test_cov_100c.py
@@ -339,1 +339,0 @@
-"endpoint": "https://user:[email protected]",
diff --git a/tests/test_cov_100g.py b/tests/test_cov_100g.py
--- a/tests/test_cov_100g.py
+++ b/tests/test_cov_100g.py
@@ -951,1 +951,0 @@
-"endpoint": "https://user:[email protected]/v1",
diff --git a/tests/test_cov_final.py b/tests/test_cov_final.py
--- a/tests/test_cov_final.py
+++ b/tests/test_cov_final.py
@@ -603,1 +603,0 @@
-cfg = {"otel": {"endpoint": "https://user:[email protected]/v1/traces"}}
diff --git a/tests/test_cov_mid.py b/tests/test_cov_mid.py
--- a/tests/test_cov_mid.py
+++ b/tests/test_cov_mid.py
@@ -141,1 +141,0 @@
-"endpoint": "https://user:[email protected]",
diff --git a/tests/test_smoke.py b/tests/test_smoke.py
--- a/tests/test_smoke.py
+++ b/tests/test_smoke.py
@@ -2567,1 +2567,0 @@
-"endpoint": "https://admin:[email protected]",
diff --git a/src/gateway_hardening.py b/src/gateway_hardening.py
--- a/src/gateway_hardening.py
+++ b/src/gateway_hardening.py
@@ -531,1 +531,0 @@
-- MEMORY.md present (warns if stale > stale_days days without update)

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 4.1.2. 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: mcp-openclaw-extensions: URL with embedded credentials (KillerSkills verdict caution 70)

## 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 70/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mcp-openclaw-extensions/4.1.2

## Findings with a location
- `tests/test_cov_100c.py:339` · URL with embedded credentials — tests/test_cov_100c.py:339 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_cov_100g.py:951` · URL with embedded credentials — tests/test_cov_100g.py:951 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_cov_final.py:603` · URL with embedded credentials — tests/test_cov_final.py:603 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_cov_mid.py:141` · URL with embedded credentials — tests/test_cov_mid.py:141 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_smoke.py:2567` · URL with embedded credentials — tests/test_smoke.py:2567 · URL with embedded credentials — may be phishing or credential leaking
- `src/gateway_hardening.py:531` · Instructs the agent to modify its persistent memory or instruction files — src/gateway_hardening.py:531 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file

## Proposed change
The attached patch removes the 6 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._