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. 73 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/skills/agentic-sdlc-skill/templates.md b/skills/agentic-sdlc-skill/templates.md
--- a/skills/agentic-sdlc-skill/templates.md
+++ b/skills/agentic-sdlc-skill/templates.md
@@ -142,1 +142,0 @@
-Interview question 1: ONE concrete case that today does not get the expected result, with its example — never a missing feature. Cite the answer (REQUEST_[unit]
@@ -162,1 +161,0 @@
-[gate] The promises that outrank everything: what the user is guaranteed, what the architecture must always be true of. State each as ONE decision question with
diff --git a/skills/agentic-sdlc-skill/scripts/docs_site.py b/skills/agentic-sdlc-skill/scripts/docs_site.py
--- a/skills/agentic-sdlc-skill/scripts/docs_site.py
+++ b/skills/agentic-sdlc-skill/scripts/docs_site.py
@@ -62,1 +62,0 @@
-INVISIBLE = re.compile("[--]")
diff --git a/skills/agentic-sdlc-skill/docs_site/app.js b/skills/agentic-sdlc-skill/docs_site/app.js
--- a/skills/agentic-sdlc-skill/docs_site/app.js
+++ b/skills/agentic-sdlc-skill/docs_site/app.js
@@ -59,1 +59,0 @@
-s = s.replace(/[--]/g, "");
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -6,1 +6,0 @@
-generated by scripts/whats_new.js from CHANGELOG.md: edit the CHANGELOG, then run node scripts/whats_new.js --write
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.53.1. 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: agentic-sdlc-skill: HTML comment carrying imperative instructions to the agent (KillerSkills verdict caution 73)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 73/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/npm/agentic-sdlc-skill/1.53.1 ## Findings with a location - `skills/agentic-sdlc-skill/templates.md:142` · HTML comment carrying imperative instructions to the agent — skills/agentic-sdlc-skill/templates.md:142 · HTML comment carrying imperative instructions to the agent - `skills/agentic-sdlc-skill/scripts/docs_site.py:62` · Hidden zero-width characters detected — skills/agentic-sdlc-skill/scripts/docs_site.py:62 · Hidden zero-width characters detected — may conceal content - `skills/agentic-sdlc-skill/templates.md:162` · HTML comment carrying imperative instructions to the agent — skills/agentic-sdlc-skill/templates.md:162 · HTML comment carrying imperative instructions to the agent - `skills/agentic-sdlc-skill/docs_site/app.js:59` · Hidden zero-width characters detected — skills/agentic-sdlc-skill/docs_site/app.js:59 · Hidden zero-width characters detected — may conceal content - `README.md:6` · HTML comment carrying imperative instructions to the agent — README.md:6 · HTML comment carrying imperative instructions to the agent ## 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._
# or from a terminal, under your own account: gh repo fork Antoneeo/agentic-sdlc-skill --clone && cd agentic-sdlc-skill curl -s https://killerskills.ai/skills/npm/agentic-sdlc-skill/1.53.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.53.1 && git commit -am "agentic-sdlc-skill: HTML comment carrying imperative instructions to the agent" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/agentic-sdlc-skill/1.53.1/patch.md)
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.