Propose a patch

Evidence

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

diff --git a/src/pmjc/defaults/model.md b/src/pmjc/defaults/model.md
--- a/src/pmjc/defaults/model.md
+++ b/src/pmjc/defaults/model.md
@@ -14,1 +14,0 @@
-e.g. "Never message anyone without asking me first", "Weekday mornings I want short answers".
diff --git a/src/pmjc/cli.py b/src/pmjc/cli.py
--- a/src/pmjc/cli.py
+++ b/src/pmjc/cli.py
@@ -365,1 +365,0 @@
-key: Optional[str] = typer.Option(None, help="private key file, e.g. ~/.ssh/id_ed25519"),
diff --git a/tests/test_tools.py b/tests/test_tools.py
--- a/tests/test_tools.py
+++ b/tests/test_tools.py
@@ -123,1 +123,0 @@
-"nas": {"host": "192.0.2.10", "user": "admin", "port": 2222, "key": "~/.ssh/id_ed25519"},
diff --git a/src/pmjc/connectors/local.py b/src/pmjc/connectors/local.py
--- a/src/pmjc/connectors/local.py
+++ b/src/pmjc/connectors/local.py
@@ -195,1 +195,0 @@
-nas:      {host: 192.0.2.10, user: admin, port: 22, key: ~/.ssh/id_ed25519}

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: pmjc: HTML comment carrying imperative instructions to the agent (KillerSkills verdict caution 54)

## 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 54/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/pmjc/0.1.0

## Findings with a location
- `src/pmjc/defaults/model.md:14` · HTML comment carrying imperative instructions to the agent — src/pmjc/defaults/model.md:14 · HTML comment carrying imperative instructions to the agent
- `src/pmjc/cli.py:365` · References a credential file in the home directory — src/pmjc/cli.py:365 · References a credential file in the home directory
- `tests/test_tools.py:123` · References a credential file in the home directory — tests/test_tools.py:123 · References a credential file in the home directory
- `src/pmjc/connectors/local.py:195` · References a credential file in the home directory — src/pmjc/connectors/local.py:195 · References a credential file in the home directory

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