Propose a patch

Evidence

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

diff --git a/assets/plugin-project-template.md b/assets/plugin-project-template.md
--- a/assets/plugin-project-template.md
+++ b/assets/plugin-project-template.md
@@ -241,1 +241,0 @@
-THE property that makes this a Rhino plugin instead of a class library. Renames the build output MyPlugin.dll -> MyPlugin.rhp. Replaces the old post-build renam
@@ -262,1 +261,0 @@
-See §4a: this also makes <Version>/<Title>/<Description>/<Company> inert. Declare that metadata in AssemblyInfo.cs instead.

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/rhino3d-plugins/1.0.1

## Findings with a location
- `assets/plugin-project-template.md:241` · HTML comment carrying imperative instructions to the agent — assets/plugin-project-template.md:241 · HTML comment carrying imperative instructions to the agent
- `assets/plugin-project-template.md:262` · HTML comment carrying imperative instructions to the agent — assets/plugin-project-template.md:262 · HTML comment carrying imperative instructions to the agent

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