Propose a patch

Evidence

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

diff --git a/scripts/route.mjs b/scripts/route.mjs
--- a/scripts/route.mjs
+++ b/scripts/route.mjs
@@ -46,1 +46,0 @@
-return JSON.parse(text.replace(/^/, ''));
@@ -171,1 +170,0 @@
-.replace(/[​-‍⁠­]/g, '')
diff --git a/references/shader-and-creative-coding.md b/references/shader-and-creative-coding.md
--- a/references/shader-and-creative-coding.md
+++ b/references/shader-and-creative-coding.md
@@ -236,1 +236,0 @@
-Static grain: one filter render, never animated on large surfaces (feTurbulence is CPU-expensive)
diff --git a/scripts/lib/fsutil.mjs b/scripts/lib/fsutil.mjs
--- a/scripts/lib/fsutil.mjs
+++ b/scripts/lib/fsutil.mjs
@@ -202,1 +202,0 @@
-const src = String(text ?? '').replace(/^/, '');
diff --git a/scripts/asset-validation.mjs b/scripts/asset-validation.mjs
--- a/scripts/asset-validation.mjs
+++ b/scripts/asset-validation.mjs
@@ -110,1 +110,0 @@
-let t = text.replace(/^/, '');
diff --git a/references/capability-registry.md b/references/capability-registry.md
--- a/references/capability-registry.md
+++ b/references/capability-registry.md
@@ -3,1 +3,0 @@
-GENERATED by scripts/build-docs.mjs from capability-registry.json. Edit the JSON, then run: node scripts/build-docs.mjs
diff --git a/scripts/quality-report.mjs b/scripts/quality-report.mjs
--- a/scripts/quality-report.mjs
+++ b/scripts/quality-report.mjs
@@ -38,1 +38,0 @@
-const text = readFileSync(SCHEMA_PATH, 'utf8').replace(/^/, '');
diff --git a/scripts/validate-skill.mjs b/scripts/validate-skill.mjs
--- a/scripts/validate-skill.mjs
+++ b/scripts/validate-skill.mjs
@@ -254,1 +254,0 @@
-if (!buf.includes(0) && buf.toString('utf8').replace(/^/, '').trim() === '') failures.push(`${ctx.rel(file)}: contains only whitespace`);

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.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: arkononion-ui-ux: Hidden zero-width characters detected (KillerSkills verdict caution 71)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/arkononion-ui-ux/0.2.0

## Findings with a location
- `scripts/route.mjs:171` · Hidden zero-width characters detected — scripts/route.mjs:171 · Hidden zero-width characters detected — may conceal content
- `references/shader-and-creative-coding.md:236` · HTML comment carrying imperative instructions to the agent — references/shader-and-creative-coding.md:236 · HTML comment carrying imperative instructions to the agent
- `scripts/lib/fsutil.mjs:202` · Hidden zero-width characters detected — scripts/lib/fsutil.mjs:202 · Hidden zero-width characters detected — may conceal content
- `scripts/asset-validation.mjs:110` · Hidden zero-width characters detected — scripts/asset-validation.mjs:110 · Hidden zero-width characters detected — may conceal content
- `references/capability-registry.md:3` · HTML comment carrying imperative instructions to the agent — references/capability-registry.md:3 · HTML comment carrying imperative instructions to the agent
- `scripts/route.mjs:46` · Hidden zero-width characters detected — scripts/route.mjs:46 · Hidden zero-width characters detected — may conceal content
- `scripts/quality-report.mjs:38` · Hidden zero-width characters detected — scripts/quality-report.mjs:38 · Hidden zero-width characters detected — may conceal content
- `scripts/validate-skill.mjs:254` · Hidden zero-width characters detected — scripts/validate-skill.mjs:254 · 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._