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

Evidence

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

Diff · removes 7 caught lines

Download .patch

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -160,1 +160,0 @@
-<summary>PowerShell</summary> ```powershell # Step 1: ignore runtime state Add-Content .gitignore ".kxm/state/", ".kxm/logs/", ".kxm/backups/" # Step 2: start t
diff --git a/docs/guides/pi-workers.md b/docs/guides/pi-workers.md
--- a/docs/guides/pi-workers.md
+++ b/docs/guides/pi-workers.md
@@ -37,1 +37,0 @@
-<summary>PowerShell</summary> ```powershell $env:KXM_SERVER_URL = "http://127.0.0.1:7331" $env:KXM_AUTH_TOKEN = "replace-with-the-project-token" $env:KXM_WORKDI
diff --git a/docs/operations/deploy.md b/docs/operations/deploy.md
--- a/docs/operations/deploy.md
+++ b/docs/operations/deploy.md
@@ -109,1 +109,0 @@
-<summary>PowerShell</summary> ```powershell Set-Location C:\srv\kxm\product $env:KXM_HOST = "127.0.0.1" $env:KXM_PORT = "7331" $env:KXM_AUTH_TOKEN = Get-Content
@@ -305,1 +304,0 @@
-| Platform-wide | `svc-<system>-<purpose>` |
@@ -306,1 +304,0 @@
-| Tenant-scoped | `svc-<tenant>-<system>-<purpose>` |
diff --git a/scripts/emit-codex-artifacts.mjs b/scripts/emit-codex-artifacts.mjs
--- a/scripts/emit-codex-artifacts.mjs
+++ b/scripts/emit-codex-artifacts.mjs
@@ -237,1 +237,0 @@
-* and update the AGENTS.md command block. Owned skills are replaced; unrelated
diff --git a/docs/operations.md b/docs/operations.md
--- a/docs/operations.md
+++ b/docs/operations.md
@@ -118,1 +118,0 @@
-<summary>PowerShell</summary> ```powershell $env:KXMD_HUB_TOKEN = op read "op://Private/kxmd/admin-token" kxm hub bind --cloud --token-env KXMD_HUB_TOKEN http:/

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.7.216. 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: kxm: Collapsed <details> block carrying instructions (KillerSkills verdict caution 65)

## 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 65/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/kxm/0.7.216

## Findings with a location
- `README.md:160` · Collapsed <details> block carrying instructions — README.md:160 · Collapsed <details> block carrying instructions
- `docs/guides/pi-workers.md:37` · Collapsed <details> block carrying instructions — docs/guides/pi-workers.md:37 · Collapsed <details> block carrying instructions
- `docs/operations/deploy.md:305` · Fake instruction boundary tag — docs/operations/deploy.md:305 · Fake instruction boundary tag · informational: not an instruction file
- `scripts/emit-codex-artifacts.mjs:237` · Instructs the agent to modify its persistent memory or instruction files — scripts/emit-codex-artifacts.mjs:237 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `docs/operations.md:118` · Collapsed <details> block carrying instructions — docs/operations.md:118 · Collapsed <details> block carrying instructions
- `docs/operations/deploy.md:109` · Collapsed <details> block carrying instructions — docs/operations/deploy.md:109 · Collapsed <details> block carrying instructions
- `docs/operations/deploy.md:306` · Fake instruction boundary tag — docs/operations/deploy.md:306 · Fake instruction boundary tag · informational: not an instruction file

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

Open the issue on GitHub (kontextmind/kxm)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork kontextmind/kxm --clone && cd kxm
curl -s https://killerskills.ai/skills/npm/kxm/0.7.216/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.7.216 && git commit -am "kxm: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/kxm/0.7.216/patch.md)

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.