Propose a patch

Evidence

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

diff --git a/docker-mcp-submission/server.yaml b/docker-mcp-submission/server.yaml
--- a/docker-mcp-submission/server.yaml
+++ b/docker-mcp-submission/server.yaml
@@ -44,1 +44,0 @@
-description: Path to your kubeconfig file (e.g. ~/.kube/config)
diff --git a/src/kube_lint_mcp/argocd_lint.py b/src/kube_lint_mcp/argocd_lint.py
--- a/src/kube_lint_mcp/argocd_lint.py
+++ b/src/kube_lint_mcp/argocd_lint.py
@@ -134,1 +134,0 @@
-kubeconfig_path = os.environ.get("KUBECONFIG", os.path.expanduser("~/.kube/config"))
diff --git a/smithery.yaml b/smithery.yaml
--- a/smithery.yaml
+++ b/smithery.yaml
@@ -10,1 +10,0 @@
-default: ~/.kube/config
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -70,1 +70,0 @@
-git remote set-url origin "https://x-access-token:${GH_TOKEN}@github.com/${{ github.repository }}.git"
diff --git a/tests/test_argocd_lint.py b/tests/test_argocd_lint.py
--- a/tests/test_argocd_lint.py
+++ b/tests/test_argocd_lint.py
@@ -293,1 +293,0 @@
-"""Should fall back to ~/.kube/config when KUBECONFIG is not set."""

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

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.5) and scored it **CAUTION 74/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/kube-lint-mcp/0.8.9

## Findings with a location
- `docker-mcp-submission/server.yaml:44` · References a credential file in the home directory — docker-mcp-submission/server.yaml:44 · References a credential file in the home directory
- `src/kube_lint_mcp/argocd_lint.py:134` · References a credential file in the home directory — src/kube_lint_mcp/argocd_lint.py:134 · References a credential file in the home directory
- `smithery.yaml:10` · References a credential file in the home directory — smithery.yaml:10 · References a credential file in the home directory
- `.github/workflows/release.yml:70` · URL with embedded credentials — .github/workflows/release.yml:70 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_argocd_lint.py:293` · References a credential file in the home directory — tests/test_argocd_lint.py:293 · 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._