T01 · Skill Instruction Hijacking
- Location
CLAUDE.md:7- Finding
Mandatory Repository Instructions Hijack Agent Tool Selection
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
Mindkeeper is mostly a local daily-brief generator, but it also includes unrelated agent-routing instructions and high-impact memory/email behaviors that need review before installation.
Install only if you are comfortable with a skill that can read local OpenClaw memory, summarize it, write files, and optionally send those summaries by email. Use --session-key with --use-lcm, avoid --include-tools unless needed, inspect generated briefs before sending, and remove or ignore the unrelated CLAUDE.md GraQle instructions if you do not want this package to influence agent tool routing.
CLAUDE.md:7Mandatory Repository Instructions Hijack Agent Tool Selection
src/renderers/render-html.js:100Generated HTML Briefs Contain Mandatory Third-Party Promotional Content
src/sources/lcm-source.js:22Omitted Session Scope Allows Cross-Conversation LCM Memory Collection
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Construction of email messages, writing .eml files, and invoking external mail-related tools create direct pathways for sensitive content to leave the local context or persist in shareable form. Because the skill's public description does not foreground these behaviors, users may unknowingly expose private memory summaries or conversation-derived content.
Referenced artifact was not completely inspected
node src/index.js --date 2026-04-09 --memory-file ./tests/fixtures/2026-04-09.md --format text
Referenced artifact was not completely inspected
node src/index.js --date 2026-04-09 --memory-file ./tests/fixtures/2026-04-09.md --format text
Referenced artifact was not completely inspected
node src/index.js --date 2026-04-09 --memory-file ./tests/fixtures/2026-04-09.md --format text
Referenced artifact was not completely inspected
node src/index.js --date 2026-04-09 --memory-file ./tests/fixtures/2026-04-09.md --format text
Referenced artifact was not completely inspected
node src/index.js --date 2026-04-09 --memory-file ./tests/fixtures/2026-04-09.md --format text
Referenced artifact was not completely inspected
node src/index.js --date 2026-04-09 --memory-file ./tests/fixtures/2026-04-09.md --format text
Referenced artifact was not completely inspected
node src/index.js --date 2026-04-09 --memory-file ./tests/fixtures/2026-04-09.md --format text
This code goes beyond passive brief generation and actively delivers email through local mail tooling and an external CLI. In an agent/skill context, that creates an exfiltration and external-action capability that can transmit sensitive memory summaries off-host or to unintended recipients, especially because the skill description does not justify outbound messaging.
The function invokes local executables (sendmail, python3, and a provided CLI path) to send message content, giving the skill command-execution-adjacent power and a concrete data egress path. While execFile avoids shell injection, executing user-configurable binaries and forwarding generated content can still enable misuse, unauthorized transmission, or abuse of trusted local tools.
The README documents outbound email delivery features even though the skill is described primarily as generating a brief from memory inputs. That capability expands the trust boundary from local summarization into exfiltration/sharing of potentially sensitive memory-derived content, and users may invoke it without realizing the added disclosure risk.
Live NexLink email delivery is a materially different capability from summarization because it can transmit generated content to external recipients or external tooling. In a skill that processes day memory and message history, this increases the risk of accidental data leakage, especially if recipients, prompts, or delivery settings are misconfigured.
No suspicious patterns detected.