Propose a patch

Evidence

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

diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
--- a/.github/workflows/deploy.yml
+++ b/.github/workflows/deploy.yml
@@ -44,1 +44,0 @@
-printf '%s\n' "$SSH_KEY" > ~/.ssh/id_ed25519 && chmod 600 ~/.ssh/id_ed25519
diff --git a/src/templates/dashboard_record.html b/src/templates/dashboard_record.html
--- a/src/templates/dashboard_record.html
+++ b/src/templates/dashboard_record.html
@@ -103,1 +103,0 @@
-<summary><span class="button">Revoke token…</span></summary> <p class="why">For a member whose token has leaked. Their token stops working at once and their rec
diff --git a/src/safety.py b/src/safety.py
--- a/src/safety.py
+++ b/src/safety.py
@@ -43,1 +43,0 @@
-"[­͏؜ᅟᅠ឴឵᠋-᠏​-‏‪-‮"
@@ -44,1 +43,0 @@
-"⁠-ㅤ︀-️ﾠ\U000e0000-\U000e007f]"
diff --git a/tests/test_safety.py b/tests/test_safety.py
--- a/tests/test_safety.py
+++ b/tests/test_safety.py
@@ -37,1 +37,0 @@
-sneaky = "For​ the‮ humans⁦\U000e0041"

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.0.0. 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: approximate-grace: References a credential file in the home directory (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/glama/approximate-grace/2.0.0

## Findings with a location
- `.github/workflows/deploy.yml:44` · References a credential file in the home directory — .github/workflows/deploy.yml:44 · References a credential file in the home directory
- `src/templates/dashboard_record.html:103` · Collapsed <details> block carrying instructions — src/templates/dashboard_record.html:103 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `src/safety.py:43` · Hidden zero-width characters detected — src/safety.py:43 · Hidden zero-width characters detected — may conceal content
- `src/safety.py:44` · Hidden zero-width characters detected — src/safety.py:44 · Hidden zero-width characters detected — may conceal content
- `tests/test_safety.py:37` · Hidden zero-width characters detected — tests/test_safety.py:37 · Hidden zero-width characters detected — may conceal content

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