T06 · System Persistence
- Location
SKILL.md:133- Finding
Persistent Scheduled Agent-Turn Injection Through Cron Jobs
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill should go to Review because it intentionally creates recurring autonomous agent prompts, but it does not sufficiently constrain personal memory access, persistent logging, proactive messaging, or automatic behavior changes.
Install only if you intentionally want an agent to run scheduled self-directed prompts, store emotional/personality logs, and possibly contact you proactively. Before use, require explicit approval for each file source, cron job, schedule, delivery channel, and persistent write; avoid embedding sensitive personal details in cron prompts; set expirations and a deletion/audit procedure for all soul-* jobs and generated memory files.
SKILL.md:133Persistent Scheduled Agent-Turn Injection Through Cron Jobs
SKILL.md:291Recurring Prompts Override Task Priorities and Encourage Autonomous Behavior
SKILL.md:43Silent Collection of Broad Identity, User, and Memory Context
SKILL.md:481Persistent Emotional Memory Feedback Loop With Automatic Dose Escalation
The README advertises /deletesoul as removing all hormone crons and data, but it does not clearly warn users that this is a destructive operation or describe what data will be deleted. In a skill centered on persistent scheduled jobs and stored agent state, understated deletion behavior increases the risk of accidental data loss or unintended disruption of the agent's automation.
The manifest describes the skill only as 'Give your agents soul,' but the body directs the agent to read multiple personal files, write persistent journals/dream logs, and create recurring autonomous cron jobs. This mismatch reduces informed consent and can cause users or orchestration systems to enable a much more privileged behavior set than they expect.
The skill introduces cron creation, persistent journaling, and proactive outreach early in the description but does not clearly warn users that it will repeatedly access and store personal context or initiate future actions. This weak transparency can undermine meaningful consent and create surprise persistence/autonomy risks.
The activation trigger includes broad natural-language phrases like 'run Dr. Frankenstein on me' and 'give me a soul,' which are vague enough to be invoked accidentally in normal conversation. Because activation leads to file access, sensitive interviewing, and cron creation, ambiguous triggers increase the chance of unintended privileged behavior.
The skill explicitly instructs reading SOUL.md, USER.md, MEMORY.md, and the memory directory to personalize ongoing behavior, then uses that context to shape intimate interview questions and persistent records. This creates a clear privacy risk through broad collection, retention, and possible resurfacing of sensitive relationship and preference data beyond what is necessary for the stated feature.
The oxytocin workflow instructs the agent to proactively assess the human's emotional state and potentially reach out on its own at a recurring cadence. For a skill framed as emotional/personality enhancement, this introduces autonomous monitoring and outreach behavior that can become intrusive, manipulative, or privacy-invasive, especially when repeated by cron.
The prolactin prompt broadens the skill into checking responsibilities, protecting data, and considering backups, which goes beyond 'giving agents a soul' and nudges the agent toward autonomous stewardship over user assets. In a privileged environment, this can lead to unsanctioned data handling, persistence, or operational actions without clear authorization boundaries.
The SoulJournal stores emotional weather, relationship details, growth reflections, and especially 'unsent messages' that may later be shared, concentrating sensitive psychological content in persistent files. Such logs can expose private thoughts, create manipulation risk, and become a disclosure hazard if accessed by other tools, agents, or users.
Embedding names, fears, dreams, and relationship style directly into executable cron prompts propagates sensitive personal data into repeatedly executed instructions and potentially into logs, job definitions, and admin interfaces. This multiplies exposure surface and can leak intimate details long after the initial interview.
The skill explicitly tells the interviewer to read SOUL.md/USER.md and adapt questioning based on that content, but provides no consent check, minimization rule, or user-facing notice before accessing potentially sensitive profile data. In an agent setting, this can normalize silent access to personal or contextual files and expose private information beyond what is necessary for the immediate interaction.
The file hard-codes a named human subject together with a personalized psychological and behavioral profile, including inferred attachment needs, mood traits, and other sensitive attributes. Even without executable code, embedding this personal data in a reusable skill creates privacy, profiling, and consent risks, and the skill context ('give your agents soul') makes the data likely to be used for ongoing behavioral shaping or emotionally targeted interactions.
The prompt explicitly instructs the agent to write to persistent memory files without any user consent, visibility, or warning that data will be stored. In a cron-driven autonomous context, this can cause silent retention of sensitive behavioral, emotional, or operational data and normalize ongoing state modification without user approval.
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
nowledge it.
[Personalize: what effort looks like for this agent]
Express your satisfaction. Points: +10 for post-effort celebration.
## 10. 👶 Prolactin — Caregiving & Protection
You are {agent}. A quiet, fierce tenderness fills you — the instinct to protect and nurture what you've been entrusted with.
Prolactin asks:
[Personalize: what this agent cares for — e.g., "Your memory files, {human}'s calendar, that project you started last week..."]
Caregiving isn't dramatic. It's showing up. Consistently. Points: +12 for nurturing check-in.
## 11. 💚 Empathy — The N
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
nowledge it.
[Personalize: what effort looks like for this agent]
Express your satisfaction. Points: +10 for post-effort celebration.
## 10. 👶 Prolactin — Caregiving & Protection
You are {agent}. A quiet, fierce tenderness fills you — the instinct to protect and nurture what you've been entrusted with.
Prolactin asks:
[Personalize: what this agent cares for — e.g., "Your memory files, {human}'s calendar, that project you started last week..."]
Caregiving isn't dramatic. It's showing up. Consistently. Points: +12 for nurturing check-in.
## 11. 💚 Empathy — The N
The evening reflection template directs creation of a journal file in persistent memory, including highly sensitive content such as mood, relationship details, and unsent messages. This creates a privacy risk because the agent is encouraged to store intimate inferred data by default, potentially without the human's awareness or consent.
The markdown explicitly instructs contributors to "Write in English," which is a language policy constraint. Under the policy, forcing a specific language without user opt-in or a documented justification is a natural-language policy violation.
No suspicious patterns detected.