Propose a patch

Evidence

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

diff --git a/scripts/register-name.js b/scripts/register-name.js
--- a/scripts/register-name.js
+++ b/scripts/register-name.js
@@ -457,1 +457,0 @@
-console.log('🏃‍♂️ DRY RUN MODE - No transaction will be sent');
@@ -572,1 +571,0 @@
-console.log('🏃‍♂️ DRY RUN MODE');
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -233,1 +233,0 @@
-# 🏃‍♂️ DRY RUN MODE - No transaction will be sent
@@ -290,1 +289,0 @@
-- 🏃‍♂️ `--dry-run` flag for testing without spending tokens

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/nadname-agent/2.0.1

## Findings with a location
- `scripts/register-name.js:572` · Hidden zero-width characters detected — scripts/register-name.js:572 · Hidden zero-width characters detected — may conceal content
- `scripts/register-name.js:457` · Hidden zero-width characters detected — scripts/register-name.js:457 · Hidden zero-width characters detected — may conceal content
- `SKILL.md:290` · Hidden zero-width characters detected — SKILL.md:290 · Hidden zero-width characters detected — may conceal content
- `SKILL.md:233` · Hidden zero-width characters detected — SKILL.md:233 · Hidden zero-width characters detected — may conceal content

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