← ragnarok-mcp@2.2.1

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

Evidence

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

Diff · removes 3 caught lines

Download .patch
diff --git a/.claude/skills/adapt-vault/SKILL.md b/.claude/skills/adapt-vault/SKILL.md
--- a/.claude/skills/adapt-vault/SKILL.md
+++ b/.claude/skills/adapt-vault/SKILL.md
@@ -245,1 +245,0 @@
-edit `~/.claude/CLAUDE.md`, show the block, then add it (adjust the vault names):
diff --git a/PKG-INFO b/PKG-INFO
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -138,1 +138,0 @@
-use them before grep, add a short instruction to your `~/.claude/CLAUDE.md` file, for example:
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -118,1 +118,0 @@
-use them before grep, add a short instruction to your `~/.claude/CLAUDE.md` file, for example:

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

## 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 79/100**. Summary: calls astral.sh only, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/ragnarok-mcp/2.2.1

## Findings with a location
- `.claude/skills/adapt-vault/SKILL.md:245` · Instructs the agent to modify its persistent memory or instruction files — .claude/skills/adapt-vault/SKILL.md:245 · Instructs the agent to modify its persistent memory or instruction files
- `PKG-INFO:138` · Instructs the agent to modify its persistent memory or instruction files — PKG-INFO:138 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `README.md:118` · Instructs the agent to modify its persistent memory or instruction files — README.md:118 · 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._
# or from a terminal, under your own account:
gh repo fork freyr/ragnarok-bundle --clone && cd ragnarok-bundle
curl -s https://killerskills.ai/skills/pypi/ragnarok-mcp/2.2.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/2.2.1 && git commit -am "ragnarok-mcp: Instructs the agent to modify its persistent memory or instruction files"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/ragnarok-mcp/2.2.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.