← subclip-hyperframes-layer@1.0.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 58 · Caution

Evidence

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

Diff · removes 10 caught lines

Download .patch
diff --git a/references/official/hyperframes-animation/rules-index.md b/references/official/hyperframes-animation/rules-index.md
--- a/references/official/hyperframes-animation/rules-index.md
+++ b/references/official/hyperframes-animation/rules-index.md
@@ -24,1 +24,0 @@
-<rules>
@@ -36,1 +35,0 @@
-</rules>
@@ -40,1 +38,0 @@
-<rules>
@@ -44,1 +41,0 @@
-</rules>
@@ -48,1 +44,0 @@
-<rules>
diff --git a/references/official/hyperframes-core/references/full-screen-motion.md b/references/official/hyperframes-core/references/full-screen-motion.md
--- a/references/official/hyperframes-core/references/full-screen-motion.md
+++ b/references/official/hyperframes-core/references/full-screen-motion.md
@@ -28,1 +28,0 @@
-Shared background — NOT a clip. Always visible. Driven by the timeline.
diff --git a/references/official/hyperframes-animation/rules/motion-blur-streak.md b/references/official/hyperframes-animation/rules/motion-blur-streak.md
--- a/references/official/hyperframes-animation/rules/motion-blur-streak.md
+++ b/references/official/hyperframes-animation/rules/motion-blur-streak.md
@@ -33,1 +33,0 @@
-Path B instead: N-1 aria-hidden .streak-ghost duplicates BEHIND the lead, no filter
diff --git a/references/official/hyperframes-animation/rules/theme-crossfade-morph.md b/references/official/hyperframes-animation/rules/theme-crossfade-morph.md
--- a/references/official/hyperframes-animation/rules/theme-crossfade-morph.md
+++ b/references/official/hyperframes-animation/rules/theme-crossfade-morph.md
@@ -37,1 +37,0 @@
-The anchor: rendered ONCE, above every skin. It never moves.
diff --git a/references/official/hyperframes-animation/rules/3d-camera-flight.md b/references/official/hyperframes-animation/rules/3d-camera-flight.md
--- a/references/official/hyperframes-animation/rules/3d-camera-flight.md
+++ b/references/official/hyperframes-animation/rules/3d-camera-flight.md
@@ -40,1 +40,0 @@
-Foreground props float at PROP_Z for parallax; they blur and fly past, never carry a read.
diff --git a/references/official/hyperframes-creative/references/composition-patterns.md b/references/official/hyperframes-creative/references/composition-patterns.md
--- a/references/official/hyperframes-creative/references/composition-patterns.md
+++ b/references/official/hyperframes-creative/references/composition-patterns.md
@@ -50,1 +50,0 @@
-z=1 base — full opaque mp4 (lobby + presenter), always visible

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: subclip-hyperframes-layer: Fake instruction boundary tag (KillerSkills verdict caution 58)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 58/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/subclip-hyperframes-layer/1.0.0

## Findings with a location
- `references/official/hyperframes-animation/rules-index.md:24` · Fake instruction boundary tag — references/official/hyperframes-animation/rules-index.md:24 · Fake instruction boundary tag · informational: not an instruction file
- `references/official/hyperframes-core/references/full-screen-motion.md:28` · HTML comment carrying imperative instructions to the agent — references/official/hyperframes-core/references/full-screen-motion.md:28 · HTML comment carrying imperative instructions to the agent
- `references/official/hyperframes-animation/rules-index.md:40` · Fake instruction boundary tag — references/official/hyperframes-animation/rules-index.md:40 · Fake instruction boundary tag · informational: not an instruction file
- `references/official/hyperframes-animation/rules/motion-blur-streak.md:33` · HTML comment carrying imperative instructions to the agent — references/official/hyperframes-animation/rules/motion-blur-streak.md:33 · HTML comment carrying imperative instructions to the agent
- `references/official/hyperframes-animation/rules-index.md:36` · Fake instruction boundary tag — references/official/hyperframes-animation/rules-index.md:36 · Fake instruction boundary tag · informational: not an instruction file
- `references/official/hyperframes-animation/rules/theme-crossfade-morph.md:37` · HTML comment carrying imperative instructions to the agent — references/official/hyperframes-animation/rules/theme-crossfade-morph.md:37 · HTML comment carrying imperative instructions to the agent
- `references/official/hyperframes-animation/rules/3d-camera-flight.md:40` · HTML comment carrying imperative instructions to the agent — references/official/hyperframes-animation/rules/3d-camera-flight.md:40 · HTML comment carrying imperative instructions to the agent
- `references/official/hyperframes-creative/references/composition-patterns.md:50` · HTML comment carrying imperative instructions to the agent — references/official/hyperframes-creative/references/composition-patterns.md:50 · HTML comment carrying imperative instructions to the agent
- `references/official/hyperframes-animation/rules-index.md:44` · Fake instruction boundary tag — references/official/hyperframes-animation/rules-index.md:44 · Fake instruction boundary tag · informational: not an instruction file
- `references/official/hyperframes-animation/rules-index.md:48` · Fake instruction boundary tag — references/official/hyperframes-animation/rules-index.md:48 · Fake instruction boundary tag · informational: not an instruction file

## Proposed change
The attached patch removes the 10 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._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.