← content-collector@2.0.1

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. 72 · Caution

Evidence

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

Diff · removes 8 caught lines

Download .patch
diff --git a/references/theme-extraction-spec.md b/references/theme-extraction-spec.md
--- a/references/theme-extraction-spec.md
+++ b/references/theme-extraction-spec.md
@@ -25,1 +25,0 @@
-<context>
@@ -29,1 +28,0 @@
-</context>
@@ -31,1 +29,0 @@
-<instructions>
@@ -37,1 +34,0 @@
-</instructions>
diff --git a/references/highlight-extraction-spec.md b/references/highlight-extraction-spec.md
--- a/references/highlight-extraction-spec.md
+++ b/references/highlight-extraction-spec.md
@@ -18,1 +18,0 @@
-<context>
@@ -22,1 +21,0 @@
-</context>
@@ -24,1 +22,0 @@
-<instructions>
@@ -32,1 +29,0 @@
-</instructions>

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/content-collector/2.0.1

## Findings with a location
- `references/theme-extraction-spec.md:25` · Fake instruction boundary tag — references/theme-extraction-spec.md:25 · Fake instruction boundary tag · informational: not an instruction file
- `references/theme-extraction-spec.md:31` · Fake instruction boundary tag — references/theme-extraction-spec.md:31 · Fake instruction boundary tag · informational: not an instruction file
- `references/highlight-extraction-spec.md:22` · Fake instruction boundary tag — references/highlight-extraction-spec.md:22 · Fake instruction boundary tag · informational: not an instruction file
- `references/theme-extraction-spec.md:37` · Fake instruction boundary tag — references/theme-extraction-spec.md:37 · Fake instruction boundary tag · informational: not an instruction file
- `references/theme-extraction-spec.md:29` · Fake instruction boundary tag — references/theme-extraction-spec.md:29 · Fake instruction boundary tag · informational: not an instruction file
- `references/highlight-extraction-spec.md:18` · Fake instruction boundary tag — references/highlight-extraction-spec.md:18 · Fake instruction boundary tag · informational: not an instruction file
- `references/highlight-extraction-spec.md:24` · Fake instruction boundary tag — references/highlight-extraction-spec.md:24 · Fake instruction boundary tag · informational: not an instruction file
- `references/highlight-extraction-spec.md:32` · Fake instruction boundary tag — references/highlight-extraction-spec.md:32 · Fake instruction boundary tag · informational: not an instruction file

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