Propose a patch

Evidence

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

diff --git a/src/redshift_comment_mcp/redshift_tools.py b/src/redshift_comment_mcp/redshift_tools.py
--- a/src/redshift_comment_mcp/redshift_tools.py
+++ b/src/redshift_comment_mcp/redshift_tools.py
@@ -425,1 +425,0 @@
-""  # BOM
@@ -426,1 +425,0 @@
-"​"  # ZERO WIDTH SPACE
@@ -427,1 +425,0 @@
-"‌"  # ZERO WIDTH NON-JOINER
@@ -428,1 +425,0 @@
-"‍"  # ZERO WIDTH JOINER
diff --git a/tests/test_tools.py b/tests/test_tools.py
--- a/tests/test_tools.py
+++ b/tests/test_tools.py
@@ -946,1 +946,0 @@
-for prefix in ('', '​', ' ', '⁠'):
@@ -959,1 +958,0 @@
-"SELECT 1",
@@ -960,1 +958,0 @@
-"​ WITH cte AS (SELECT 1 x) SELECT * FROM cte",
@@ -979,1 +976,0 @@
-("​   ", "Empty"),

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.12.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: redshift-comment-mcp: Hidden zero-width characters detected (KillerSkills verdict caution 68)

## 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 68/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/redshift-comment-mcp/0.12.0

## Findings with a location
- `src/redshift_comment_mcp/redshift_tools.py:426` · Hidden zero-width characters detected — src/redshift_comment_mcp/redshift_tools.py:426 · Hidden zero-width characters detected — may conceal content
- `src/redshift_comment_mcp/redshift_tools.py:425` · Hidden zero-width characters detected — src/redshift_comment_mcp/redshift_tools.py:425 · Hidden zero-width characters detected — may conceal content
- `src/redshift_comment_mcp/redshift_tools.py:428` · Hidden zero-width characters detected — src/redshift_comment_mcp/redshift_tools.py:428 · Hidden zero-width characters detected — may conceal content
- `src/redshift_comment_mcp/redshift_tools.py:427` · Hidden zero-width characters detected — src/redshift_comment_mcp/redshift_tools.py:427 · Hidden zero-width characters detected — may conceal content
- `tests/test_tools.py:959` · Hidden zero-width characters detected — tests/test_tools.py:959 · Hidden zero-width characters detected — may conceal content
- `tests/test_tools.py:946` · Hidden zero-width characters detected — tests/test_tools.py:946 · Hidden zero-width characters detected — may conceal content
- `tests/test_tools.py:960` · Hidden zero-width characters detected — tests/test_tools.py:960 · Hidden zero-width characters detected — may conceal content
- `tests/test_tools.py:979` · Hidden zero-width characters detected — tests/test_tools.py:979 · Hidden zero-width characters detected — may conceal content

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