← fractal-memory@1.0.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. 67 · Caution

Evidence

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

Diff · removes 9 caught lines

Download .patch
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -56,1 +56,0 @@
-Add to your AGENTS.md:
@@ -124,1 +123,0 @@
-Distill major themes, lessons learned → update `MEMORY.md`
diff --git a/references/migration-guide.md b/references/migration-guide.md
--- a/references/migration-guide.md
+++ b/references/migration-guide.md
@@ -55,1 +55,0 @@
-### 5. Update AGENTS.md
@@ -93,1 +92,0 @@
-Your existing MEMORY.md stays at the workspace root. The monthly rollup will append to it.
@@ -175,1 +173,0 @@
-### 3. Update AGENTS.md
diff --git a/references/architecture.md b/references/architecture.md
--- a/references/architecture.md
+++ b/references/architecture.md
@@ -66,1 +66,0 @@
-- Update MEMORY.md with key insights
@@ -147,1 +146,0 @@
-- [ ] Update AGENTS.md to reference new structure
diff --git a/scripts/rollup-monthly.py b/scripts/rollup-monthly.py
--- a/scripts/rollup-monthly.py
+++ b/scripts/rollup-monthly.py
@@ -81,1 +81,0 @@
-"""Update MEMORY.md with monthly insights"""
@@ -143,1 +142,0 @@
-# Update MEMORY.md

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/fractal-memory/1.0.0

## Findings with a location
- `SKILL.md:56` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:56 · Instructs the agent to modify its persistent memory or instruction files
- `references/migration-guide.md:93` · Instructs the agent to modify its persistent memory or instruction files — references/migration-guide.md:93 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `SKILL.md:124` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:124 · Instructs the agent to modify its persistent memory or instruction files
- `references/migration-guide.md:175` · Instructs the agent to modify its persistent memory or instruction files — references/migration-guide.md:175 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `references/migration-guide.md:55` · Instructs the agent to modify its persistent memory or instruction files — references/migration-guide.md:55 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `references/architecture.md:147` · Instructs the agent to modify its persistent memory or instruction files — references/architecture.md:147 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `references/architecture.md:66` · Instructs the agent to modify its persistent memory or instruction files — references/architecture.md:66 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `scripts/rollup-monthly.py:143` · Instructs the agent to modify its persistent memory or instruction files — scripts/rollup-monthly.py:143 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `scripts/rollup-monthly.py:81` · Instructs the agent to modify its persistent memory or instruction files — scripts/rollup-monthly.py:81 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

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