Propose a patch

Evidence

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

diff --git a/references/patch-spec.md b/references/patch-spec.md
--- a/references/patch-spec.md
+++ b/references/patch-spec.md
@@ -43,1 +43,0 @@
-<instruction>
@@ -50,1 +49,0 @@
-</instruction>
@@ -74,1 +72,0 @@
-<instruction>...</instruction>
@@ -86,1 +83,0 @@
-<instruction>

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.2. 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: moa-engine: Fake instruction boundary tag (KillerSkills verdict caution 71)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/moa-engine/1.0.2

## Findings with a location
- `references/patch-spec.md:43` · Fake instruction boundary tag — references/patch-spec.md:43 · Fake instruction boundary tag · informational: not an instruction file
- `references/patch-spec.md:50` · Fake instruction boundary tag — references/patch-spec.md:50 · Fake instruction boundary tag · informational: not an instruction file
- `references/patch-spec.md:74` · Fake instruction boundary tag — references/patch-spec.md:74 · Fake instruction boundary tag · informational: not an instruction file
- `references/patch-spec.md:86` · Fake instruction boundary tag — references/patch-spec.md:86 · Fake instruction boundary tag · informational: not an instruction file

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