Propose a patch

Evidence

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

diff --git a/src/index.ts b/src/index.ts
--- a/src/index.ts
+++ b/src/index.ts
@@ -25,1 +25,0 @@
-KUBECONFIG              absolute path to the kubeconfig (default: ~/.kube/config)
diff --git a/src/setup.ts b/src/setup.ts
--- a/src/setup.ts
+++ b/src/setup.ts
@@ -259,1 +259,0 @@
-fix: ["Point it at an existing file, or remove it to use ~/.kube/config"],
@@ -274,1 +273,0 @@
-what: "No kubeconfig found (KUBECONFIG not set, ~/.kube/config missing)",
diff --git a/claude-desktop/manifest.json b/claude-desktop/manifest.json
--- a/claude-desktop/manifest.json
+++ b/claude-desktop/manifest.json
@@ -54,1 +54,0 @@
-"default": "${HOME}/.kube/config"
diff --git a/test/setup.test.ts b/test/setup.test.ts
--- a/test/setup.test.ts
+++ b/test/setup.test.ts
@@ -48,1 +48,0 @@
-const s = loadSetup({ KUBECONFIG: "~/.kube/config" });

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.0.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: k8s-cronjob-mcp: References a credential file in the home directory (KillerSkills verdict caution 75)

## 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 75/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/k8s-cronjob-mcp/2.0.2

## Findings with a location
- `src/index.ts:25` · References a credential file in the home directory — src/index.ts:25 · References a credential file in the home directory
- `src/setup.ts:274` · References a credential file in the home directory — src/setup.ts:274 · References a credential file in the home directory
- `src/setup.ts:259` · References a credential file in the home directory — src/setup.ts:259 · References a credential file in the home directory
- `claude-desktop/manifest.json:54` · References a credential file in the home directory — claude-desktop/manifest.json:54 · References a credential file in the home directory
- `test/setup.test.ts:48` · References a credential file in the home directory — test/setup.test.ts:48 · References a credential file in the home directory

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