Propose a patch

Evidence

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

diff --git a/src/secrets/guard.ts b/src/secrets/guard.ts
--- a/src/secrets/guard.ts
+++ b/src/secrets/guard.ts
@@ -75,1 +75,0 @@
-* token(s) key the value must also pass tokenValueOk (0.11.2).
diff --git a/src/stdio.ts b/src/stdio.ts
--- a/src/stdio.ts
+++ b/src/stdio.ts
@@ -61,1 +61,0 @@
-const BOM = '';
diff --git a/examples/README.md b/examples/README.md
--- a/examples/README.md
+++ b/examples/README.md
@@ -17,1 +17,0 @@
-and add the line from `examples/.claude/CLAUDE.md` to your `CLAUDE.md`.

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.11.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: kronicle-lite: Credential pass-through configuration (KillerSkills verdict caution 68)

## 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 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/kronicle-lite/0.11.2

## Findings with a location
- `src/secrets/guard.ts:75` · Credential pass-through configuration — src/secrets/guard.ts:75 · Credential pass-through configuration — agent relays sensitive credentials
- `src/stdio.ts:61` · Hidden zero-width characters detected — src/stdio.ts:61 · Hidden zero-width characters detected — may conceal content
- `examples/README.md:17` · Instructs the agent to modify its persistent memory or instruction files — examples/README.md:17 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

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