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 3 caught lines
Download .patchdiff --git a/dist/agent/install.js b/dist/agent/install.js
--- a/dist/agent/install.js
+++ b/dist/agent/install.js
@@ -10,1 +10,0 @@
-{ id: 'agents-md', status: 'provisional', note: 'a section in AGENTS.md, with --write-agents-md' },
diff --git a/dist/robots/robots.js b/dist/robots/robots.js
--- a/dist/robots/robots.js
+++ b/dist/robots/robots.js
@@ -13,1 +13,0 @@
-const lines = body.replace(/^/, '').split(/\r\n|\r|\n/);
diff --git a/dist/sitemap/sitemap.js b/dist/sitemap/sitemap.js
--- a/dist/sitemap/sitemap.js
+++ b/dist/sitemap/sitemap.js
@@ -14,1 +14,0 @@
-const text = xml.replace(/^/, '').replace(/<!--[\s\S]*?-->/g, '');
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.0.4. 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: geopilot: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 72)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 72/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/geopilot/0.0.4 ## Findings with a location - `dist/agent/install.js:10` · Instructs the agent to modify its persistent memory or instruction files — dist/agent/install.js:10 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `dist/robots/robots.js:13` · Hidden zero-width characters detected — dist/robots/robots.js:13 · Hidden zero-width characters detected — may conceal content - `dist/sitemap/sitemap.js:14` · Hidden zero-width characters detected — dist/sitemap/sitemap.js:14 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 3 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._
# or from a terminal, under your own account: gh repo fork moelzanaty3/geopilot --clone && cd geopilot curl -s https://killerskills.ai/skills/npm/geopilot/0.0.4/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.0.4 && git commit -am "geopilot: Instructs the agent to modify its persistent memory or instruction files" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/geopilot/0.0.4/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.