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

Evidence

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

Diff · removes 3 caught lines

Download .patch

diff --git a/README.ja.md b/README.ja.md
--- a/README.ja.md
+++ b/README.ja.md
@@ -298,1 +298,0 @@
-<summary><strong>ルールを追加する</strong></summary> ルールは [`rules.json`](rules.json) にあります：`id`、`area`、`severity`、そして `en` と `tr` の `title`、`rule`、`why`、`fix`、さらに任意の `c
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -419,1 +419,0 @@
-<summary><strong>Adding a rule</strong></summary> Rules live in [`rules.json`](rules.json): `id`, `area`, `severity`, and `title`, `rule`, `why` and `fix` in `e
diff --git a/README.tr.md b/README.tr.md
--- a/README.tr.md
+++ b/README.tr.md
@@ -426,1 +426,0 @@
-<summary><strong>Kural ekleme</strong></summary> Kurallar [`rules.json`](rules.json) içinde: `id`, `area`, `severity`, `en` ve `tr` altında `title`, `rule`, `wh

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

## 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 68/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/ai-design-check/0.16.1

## Findings with a location
- `README.ja.md:298` · Collapsed <details> block carrying instructions — README.ja.md:298 · Collapsed <details> block carrying instructions
- `README.md:419` · Collapsed <details> block carrying instructions — README.md:419 · Collapsed <details> block carrying instructions
- `README.tr.md:426` · Collapsed <details> block carrying instructions — README.tr.md:426 · Collapsed <details> block carrying instructions

## 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._

Open the issue on GitHub (enmerasoftware/ai-design-check)Fork to open a PR

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