Propose a patch

Evidence

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

diff --git a/servers/gpaw-computation/README.md b/servers/gpaw-computation/README.md
--- a/servers/gpaw-computation/README.md
+++ b/servers/gpaw-computation/README.md
@@ -7,1 +7,0 @@
-<summary>How to install uv?</summary> For macOS and Linux: ```bash curl -LsSf https://astral.sh/uv/install.sh | sh ``` For Windows: ```powershell powershell -Ex
@@ -47,1 +46,0 @@
-prettier-ignore-start
@@ -67,1 +65,0 @@
-prettier-ignore-end
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -208,1 +208,0 @@
-<summary>👈 Click to see more conventions about directory and naming</summary> Please create your new server in the `servers` folder. For creating a new server 
diff --git a/servers/materials-project/README.md b/servers/materials-project/README.md
--- a/servers/materials-project/README.md
+++ b/servers/materials-project/README.md
@@ -201,1 +201,0 @@
-prettier-ignore-start
@@ -222,1 +221,0 @@
-prettier-ignore-end

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mcp.science/0.1.7

## Findings with a location
- `servers/gpaw-computation/README.md:7` · Collapsed <details> block carrying instructions — servers/gpaw-computation/README.md:7 · Collapsed <details> block carrying instructions
- `servers/gpaw-computation/README.md:47` · HTML comment carrying imperative instructions to the agent — servers/gpaw-computation/README.md:47 · HTML comment carrying imperative instructions to the agent
- `README.md:208` · Collapsed <details> block carrying instructions — README.md:208 · Collapsed <details> block carrying instructions
- `servers/materials-project/README.md:201` · HTML comment carrying imperative instructions to the agent — servers/materials-project/README.md:201 · HTML comment carrying imperative instructions to the agent
- `servers/gpaw-computation/README.md:67` · HTML comment carrying imperative instructions to the agent — servers/gpaw-computation/README.md:67 · HTML comment carrying imperative instructions to the agent
- `servers/materials-project/README.md:222` · HTML comment carrying imperative instructions to the agent — servers/materials-project/README.md:222 · HTML comment carrying imperative instructions to the agent

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