Propose a patch

Evidence

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

diff --git a/scripts/gitea_api.py b/scripts/gitea_api.py
--- a/scripts/gitea_api.py
+++ b/scripts/gitea_api.py
@@ -1,1 +1,0 @@
-import base64
diff --git a/setup.sh b/setup.sh
--- a/setup.sh
+++ b/setup.sh
@@ -1,1 +1,0 @@
-#!/usr/bin/env bash
diff --git a/main.js b/main.js
--- a/main.js
+++ b/main.js
@@ -1,1 +1,0 @@
-module.exports = {
diff --git a/scripts/run_task.py b/scripts/run_task.py
--- a/scripts/run_task.py
+++ b/scripts/run_task.py
@@ -1,1 +1,0 @@
-import argparse
diff --git a/scripts/text_extractors.py b/scripts/text_extractors.py
--- a/scripts/text_extractors.py
+++ b/scripts/text_extractors.py
@@ -1,1 +1,0 @@
-import xml.etree.ElementTree as ET
diff --git a/scripts/query_context.py b/scripts/query_context.py
--- a/scripts/query_context.py
+++ b/scripts/query_context.py
@@ -1,1 +1,0 @@
-from catalog import catalog_from_raw, visible_catalog_pages
diff --git a/scripts/catalog.py b/scripts/catalog.py
--- a/scripts/catalog.py
+++ b/scripts/catalog.py
@@ -1,1 +1,0 @@
-import json

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.8. 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: kb-query: Hidden zero-width characters detected (KillerSkills verdict caution 60)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/kb-query/1.0.8

## Findings with a location
- `scripts/gitea_api.py:1` · Hidden zero-width characters detected — scripts/gitea_api.py:1 · Hidden zero-width characters detected — may conceal content
- `setup.sh:1` · Hidden zero-width characters detected — setup.sh:1 · Hidden zero-width characters detected — may conceal content
- `main.js:1` · Hidden zero-width characters detected — main.js:1 · Hidden zero-width characters detected — may conceal content
- `scripts/run_task.py:1` · Hidden zero-width characters detected — scripts/run_task.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/text_extractors.py:1` · Hidden zero-width characters detected — scripts/text_extractors.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/query_context.py:1` · Hidden zero-width characters detected — scripts/query_context.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/catalog.py:1` · Hidden zero-width characters detected — scripts/catalog.py:1 · Hidden zero-width characters detected — may conceal content

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