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. 72 · Caution

Evidence

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

Diff · removes 6 caught lines

Download .patch

diff --git a/pricing-models.md b/pricing-models.md
--- a/pricing-models.md
+++ b/pricing-models.md
@@ -94,1 +94,0 @@
-…n a price, product, coupon or promotion code is created, retired or replaced**, write its row to `## Catalog` in `~/Clawic/data/stripe-api-integration/memory.md` — id, model, amount with currency, interval, what it replaced — in the same tu…
diff --git a/debug.md b/debug.md
--- a/debug.md
+++ b/debug.md
@@ -99,1 +99,0 @@
-…f the fix produced a procedure, save it as `artifacts/runbook-<symptom>.md` and add its `## Boxes` line to `memory.md` in the same turn. The second occurrence of a symptom should cost minutes, not …
diff --git a/memory-template.md b/memory-template.md
--- a/memory-template.md
+++ b/memory-template.md
@@ -49,1 +49,0 @@
-…`, move the whole section into it, **delete the section from `memory.md`**, and add its line to `## Boxes`. `memory.md` keeps the index line and nothing else. 4. **Precedence**: never leave a copy b…
diff --git a/dunning.md b/dunning.md
--- a/dunning.md
+++ b/dunning.md
@@ -91,1 +91,0 @@
-… the retry schedule, grace period or terminal behavior is decided or changed**, write it to `## Integration Shape` in `~/Clawic/data/stripe-api-integration/memory.md`, and save the reasoning — attempt count against price point, measured recovery…
diff --git a/sca-3ds.md b/sca-3ds.md
--- a/sca-3ds.md
+++ b/sca-3ds.md
@@ -86,1 +86,0 @@
-… blanket 3DS, exemption-first, per-segment rules, or a specific recovery flow — write it to `## Integration Shape` in `~/Clawic/data/stripe-api-integration/memory.md`, and if the reasoning took work (fraud rate by segment, conversion measured ag…
diff --git a/api-mechanics.md b/api-mechanics.md
--- a/api-mechanics.md
+++ b/api-mechanics.md
@@ -97,1 +97,0 @@
-… the idempotency-key convention or the metadata schema is decided or changed**, write it to `## Integration Shape` in `~/Clawic/data/stripe-api-integration/memory.md`, and record the convention itself under `conventions` in `config.yaml` — it is…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.4. 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: stripe-api-integration: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 72)

## 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 72/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/stripe-api-integration/1.0.4

## Findings with a location
- `pricing-models.md:94` · Instructs the agent to modify its persistent memory or instruction files — pricing-models.md:94 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `debug.md:99` · Instructs the agent to modify its persistent memory or instruction files — debug.md:99 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `memory-template.md:49` · Instructs the agent to modify its persistent memory or instruction files — memory-template.md:49 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `dunning.md:91` · Instructs the agent to modify its persistent memory or instruction files — dunning.md:91 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `sca-3ds.md:86` · Instructs the agent to modify its persistent memory or instruction files — sca-3ds.md:86 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `api-mechanics.md:97` · Instructs the agent to modify its persistent memory or instruction files — api-mechanics.md:97 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

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