Propose a patch

Evidence

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

diff --git a/templates/viewer.html b/templates/viewer.html
--- a/templates/viewer.html
+++ b/templates/viewer.html
@@ -2,1 +2,0 @@
-THIS IS A TEMPLATE THAT SHOULD BE USED EVERY TIME AND MODIFIED. WHAT TO KEEP: ✓ Overall structure (header, sidebar, main content) ✓ Anthropic branding (colors, 
@@ -339,1 +338,0 @@
-Seed Section (ALWAYS KEEP THIS)
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -279,1 +279,0 @@
-p5.js from CDN - always available

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: algorithmic-art: HTML comment carrying imperative instructions to the agent (KillerSkills verdict caution 65)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/algorithmic-art/1.0.0

## Findings with a location
- `templates/viewer.html:2` · HTML comment carrying imperative instructions to the agent — templates/viewer.html:2 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file
- `SKILL.md:279` · HTML comment carrying imperative instructions to the agent — SKILL.md:279 · HTML comment carrying imperative instructions to the agent
- `templates/viewer.html:339` · HTML comment carrying imperative instructions to the agent — templates/viewer.html:339 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file

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