Propose a patch

Evidence

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

diff --git a/tests/test-safety-gates.sh b/tests/test-safety-gates.sh
--- a/tests/test-safety-gates.sh
+++ b/tests/test-safety-gates.sh
@@ -117,1 +117,0 @@
-dest "userinfo host confusion refused"   block 'https://allowed.example:[email protected]' allowed.example
diff --git a/scripts/wp-credentials.sh b/scripts/wp-credentials.sh
--- a/scripts/wp-credentials.sh
+++ b/scripts/wp-credentials.sh
@@ -90,1 +90,0 @@
-# host out with shell substring ops, so `https://allowed.example:[email protected]`

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.4.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: wordpress-ultimate: URL with embedded credentials (KillerSkills verdict caution 79)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/wordpress-ultimate/1.4.0

## Findings with a location
- `tests/test-safety-gates.sh:117` · URL with embedded credentials — tests/test-safety-gates.sh:117 · URL with embedded credentials — may be phishing or credential leaking
- `scripts/wp-credentials.sh:90` · URL with embedded credentials — scripts/wp-credentials.sh:90 · URL with embedded credentials — may be phishing or credential leaking

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