Propose a patch

Evidence

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

diff --git a/scripts/ga4_report.py b/scripts/ga4_report.py
--- a/scripts/ga4_report.py
+++ b/scripts/ga4_report.py
@@ -30,1 +30,0 @@
-@import url('https://fonts.googleapis.com/css2?family=Manrope:wght@400;500;600;700&display=swap');
@@ -178,1 +177,0 @@
-@import url('https://fonts.googleapis.com/css2?family=Manrope:wght@400;500;600;700&display=swap');
diff --git a/scripts/test_ga4_pinned_fetch.py b/scripts/test_ga4_pinned_fetch.py
--- a/scripts/test_ga4_pinned_fetch.py
+++ b/scripts/test_ga4_pinned_fetch.py
@@ -97,1 +97,0 @@
-context.assert_fetchable("https://username:[email protected]/")

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.5.3. 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: google-analytics-agent: URL with embedded credentials (KillerSkills verdict caution 74)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/google-analytics-agent/0.5.3

## Findings with a location
- `scripts/ga4_report.py:30` · URL with embedded credentials — scripts/ga4_report.py:30 · URL with embedded credentials — may be phishing or credential leaking
- `scripts/ga4_report.py:178` · URL with embedded credentials — scripts/ga4_report.py:178 · URL with embedded credentials — may be phishing or credential leaking
- `scripts/test_ga4_pinned_fetch.py:97` · URL with embedded credentials — scripts/test_ga4_pinned_fetch.py:97 · URL with embedded credentials — may be phishing or credential leaking

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