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 4 caught lines
Download .patchdiff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -187,1 +187,0 @@ -<rules> @@ -194,1 +193,0 @@ -</rules> @@ -228,1 +226,0 @@ -<rules> @@ -235,1 +232,0 @@ -</rules>
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: modal-mcpdoc: 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.8.1) 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/pypi/modal-mcpdoc/0.1.2 ## Findings with a location - `README.md:235` · Fake instruction boundary tag — README.md:235 · Fake instruction boundary tag · informational: not an instruction file - `README.md:187` · Fake instruction boundary tag — README.md:187 · Fake instruction boundary tag · informational: not an instruction file - `README.md:194` · Fake instruction boundary tag — README.md:194 · Fake instruction boundary tag · informational: not an instruction file - `README.md:228` · Fake instruction boundary tag — README.md:228 · 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._
# or from a terminal, under your own account: gh repo fork langchain-ai/mcpdoc --clone && cd mcpdoc curl -s https://killerskills.ai/skills/pypi/modal-mcpdoc/0.1.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.2 && git commit -am "modal-mcpdoc: Fake instruction boundary tag" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/modal-mcpdoc/0.1.2/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.