← persistent-code-terminal@1.2.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 65 · Caution

Evidence

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

Diff · removes 11 caught lines

Download .patch
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -38,1 +38,0 @@
-- `给 <project> 项目 <instruction>`
@@ -39,1 +38,0 @@
-- `给<project>项目:<instruction>`
@@ -44,1 +42,0 @@
-- `auto.sh --max-retries 3 --instruction "<instruction>"`
@@ -58,1 +55,0 @@
-- `codex-exec.sh "<instruction>"` for Codex-driven work
@@ -99,1 +95,0 @@
-- `{baseDir}/bin/persistent-code-terminal-codex-exec.sh "<instruction>"`
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -108,1 +108,0 @@
-- In OpenClaw routing, map `codex <instruction>` to:
@@ -109,1 +108,0 @@
-- `./skills/persistent-code-terminal/bin/persistent-code-terminal-codex-exec.sh "<instruction>"`
@@ -169,1 +167,0 @@
-- `给 <project> 项目 <instruction>`
@@ -170,1 +167,0 @@
-- `给<project>项目:<instruction>`
@@ -181,1 +177,0 @@
-- run `persistent-code-terminal-auto.sh --max-retries 3 --instruction "<instruction>"`
diff --git a/RELEASE.md b/RELEASE.md
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -12,1 +12,0 @@
-- `codex exec --full-auto --sandbox workspace-write --cd <current-dir> "<instruction>"`

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.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: persistent-code-terminal: Fake instruction boundary tag (KillerSkills verdict caution 65)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 65/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/persistent-code-terminal/1.2.0

## Findings with a location
- `SKILL.md:38` · Fake instruction boundary tag — SKILL.md:38 · Fake instruction boundary tag
- `SKILL.md:58` · Fake instruction boundary tag — SKILL.md:58 · Fake instruction boundary tag
- `README.md:181` · Fake instruction boundary tag — README.md:181 · Fake instruction boundary tag · informational: not an instruction file
- `RELEASE.md:12` · Fake instruction boundary tag — RELEASE.md:12 · Fake instruction boundary tag · informational: not an instruction file
- `SKILL.md:99` · Fake instruction boundary tag — SKILL.md:99 · Fake instruction boundary tag
- `README.md:108` · Fake instruction boundary tag — README.md:108 · Fake instruction boundary tag · informational: not an instruction file
- `SKILL.md:44` · Fake instruction boundary tag — SKILL.md:44 · Fake instruction boundary tag
- `README.md:109` · Fake instruction boundary tag — README.md:109 · Fake instruction boundary tag · informational: not an instruction file
- `SKILL.md:39` · Fake instruction boundary tag — SKILL.md:39 · Fake instruction boundary tag
- `README.md:170` · Fake instruction boundary tag — README.md:170 · Fake instruction boundary tag · informational: not an instruction file
- `README.md:169` · Fake instruction boundary tag — README.md:169 · Fake instruction boundary tag · informational: not an instruction file

## Proposed change
The attached patch removes the 11 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._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.