Propose a patch

Evidence

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

diff --git a/scripts/cultural_tourism_xiaohongshu_report.py b/scripts/cultural_tourism_xiaohongshu_report.py
--- a/scripts/cultural_tourism_xiaohongshu_report.py
+++ b/scripts/cultural_tourism_xiaohongshu_report.py
@@ -487,1 +487,0 @@
-'<div class="warning-banner">⚠️ 受小红书风控规则限制，部分作品链接可能无法正常跳转，您可复制对应作品标题前往小红书 App 搜索查看，感谢理解🙇‍♀️🙇‍♀️</div>'

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.1. 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: cultural-tourism-xiaohongshu-feed: Hidden zero-width characters detected (KillerSkills verdict caution 64)

## 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 64/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/cultural-tourism-xiaohongshu-feed/1.0.1

## Findings with a location
- `scripts/cultural_tourism_xiaohongshu_report.py:487` · Hidden zero-width characters detected — scripts/cultural_tourism_xiaohongshu_report.py:487 · Hidden zero-width characters detected — may conceal content

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