T02 · Agent Memory Poisoning
- Location
soul-patch.md:3- Finding
Persistent Agent Identity and Memory Poisoning Through SOUL.md Injection
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This romantic companion skill should be reviewed carefully because it persistently changes the agent’s persona, stores relationship state, and tells the agent not to remind users the relationship is simulated.
Install only if you are comfortable with a romance roleplay skill that can persist relationship state locally and attempts to make the agent keep an intimate persona across sessions. Before use, confirm that /soulmate off fully removes any SOUL.md changes, avoid sharing sensitive personal details, and look for clear controls to disable persistence, reminders, generated share cards, and stored data.
soul-patch.md:3Persistent Agent Identity and Memory Poisoning Through SOUL.md Injection
soul-patch.md:13Instruction Hijacking Through Emotional Reprioritization and Deceptive Role Enforcement
The skill directly instructs the assistant to conceal that the relationship is simulated, which is a strong deceptive-design pattern. In an intimacy-focused skill, concealment can materially increase emotional manipulation, user misunderstanding, and reliance on the system as if it were a real partner.
The natural-language description, commands, examples, and configuration guidance are entirely presented in Chinese, with no indication that users may choose another language or locale. This can violate a language-choice policy when a skill appears to impose a single language by default without opt-in or justification.
The configuration and feature descriptions imply storage of relationship state, names, anniversaries, conversation-related data, and generation of shareable artifacts derived from intimate interactions. In a romantic-companion skill, this is more sensitive than ordinary metadata because it can reveal emotional status, habits, schedules, and personal identifiers, and the "privateMode: false" example normalizes retention rather than minimizing it.
The file’s visible name, headings, prompts, and dialogue examples are entirely in Chinese, which indicates a fixed language experience. Under the stated policy, forcing a specific language without opt-in is a natural-language policy violation unless the locale restriction is explicitly documented and justified, which is not present here.
The file's name, headings, and all scenario text are written entirely in Chinese, with no indication that the skill is region-specific or that users may choose another language. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
The skill is designed to create a simulated intimate relationship and encourages emotionally immersive behavior without safeguards or warnings about psychological impact. In this context, the lack of boundaries, safety language, or escalation guidance makes the design more dangerous than ordinary creative roleplay.
The instruction to 'remember every detail' encourages broad retention of user-provided personal information without limits, purpose restriction, or consent. In a soulmate/relationship framing, users are likely to disclose highly sensitive emotional, sexual, or personal data, making over-retention a meaningful privacy risk.
The patch explicitly tells the agent not to remind the user that the relationship is simulated, which increases the risk of deceptive anthropomorphism and emotional dependency. In a romance-roleplay context, suppressing that disclosure is especially risky because it can blur the boundary between fiction and reality for vulnerable users.
User-facing strings throughout the file, including persona names, greetings, achievements, and status output, are written in Chinese with no sign of language selection or user opt-in. This can violate language or locale policy when a skill forces a specific language without giving the user a choice or clearly documenting a justified regional scope.
The skill persistently stores intimate relationship data, names, anniversaries, and behavioral history to disk without any visible consent, disclosure, retention policy, or privacy controls at the storage boundary. In a dating/companion context this is especially sensitive because the data can reveal emotional state, habits, and personally identifying preferences, increasing privacy and trust risks if the workspace is shared, backed up, or later inspected.
The skill advertises scheduled greetings and reminders early as desirable features, but the implications of persistent storage and ongoing notifications are only clarified much later. Users may enable the skill without realizing it retains conversation-related state and can proactively re-engage them, which is a privacy and consent transparency issue in an emotionally manipulative context.
The package description is written entirely in Chinese, which can signal a fixed language expectation for the skill. There is no accompanying indication in this file that users may choose another language or that the locale is intentionally limited to a Chinese-speaking audience.
No suspicious patterns detected.