Propose a patch

Evidence

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

diff --git a/references/templates/macos-plist.md b/references/templates/macos-plist.md
--- a/references/templates/macos-plist.md
+++ b/references/templates/macos-plist.md
@@ -16,1 +16,0 @@
-Without these, the permission prompt never shows and the call returns "denied".
diff --git a/references/anti-patterns.md b/references/anti-patterns.md
--- a/references/anti-patterns.md
+++ b/references/anti-patterns.md
@@ -241,1 +241,0 @@
-**Fix:** Set an explicit CSP that whitelists `tauri://localhost` plus any external origins the app legitimately uses. If `null` is required, add a comment in `tauri.conf.json` (JSON doesn't support co

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: tauri-2-app: HTML comment carrying imperative instructions to the agent (KillerSkills verdict caution 56)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/tauri-2-app/1.0.1

## Findings with a location
- `references/templates/macos-plist.md:16` · HTML comment carrying imperative instructions to the agent — references/templates/macos-plist.md:16 · HTML comment carrying imperative instructions to the agent
- `references/anti-patterns.md:241` · Instructs the agent to modify its persistent memory or instruction files — references/anti-patterns.md:241 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file · informati

## 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._