T01 · Skill Instruction Hijacking
- Location
SKILL.md:60- Finding
Untrusted Batch and Drive Content Can Be Executed as Agent Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a batch prompt executor, but it stores complete user or Drive content indefinitely and can execute imported document text without clear confirmation boundaries.
Review before installing. Use it only for batches and Drive folders you are comfortable copying into local workspace files and reusing across sessions. Avoid secrets, credentials, regulated data, or confidential documents unless retention, deletion, redaction, and explicit confirmation rules are added.
SKILL.md:60Untrusted Batch and Drive Content Can Be Executed as Agent Instructions
references/rolling-decay-memory.md:45Complete Batch Content Is Persisted Indefinitely Without Sensitive-Data Controls
The skill explicitly supports Drive and file-based ingestion but gives no warning about handling potentially sensitive external documents. That combination can lead to large-scale ingestion of confidential data into persistent local memory structures without informed consent or minimization.
The skill mandates saving the entire batch to persistent files before processing, but it does not warn users that their content will be stored and replicated in local artifacts. This is dangerous because users may paste sensitive prompts, credentials, business data, or personal information expecting transient handling rather than durable storage.
The self-improvement section allows the skill to change itself based on prior runs, which is not necessary for batch processing and introduces unauthorized behavior drift. In practice, this can weaken safeguards over time, embed tainted lessons from adversarial input, and make the skill's future behavior less predictable and less auditable.
The directive to 'Update this skill if any rule changes warranted' is explicit self-modification authority. Self-modifying skills are especially dangerous because untrusted batch inputs can indirectly influence future behavior, alter safeguards, and create persistence for adversarial instructions beyond the current session.
After each batch, append to `workspace/systems/batch-cognition/learnings.md`:
- What worked / what was wasted / grouping improvements / play-think split effectiveness
- Update this skill if any rule changes warranted.
## Key Rules
The activation scope covers vague patterns like bulk input, file-based lists, and Drive dumps, which can easily match ordinary user behavior and trigger the skill unexpectedly. Over-broad activation is dangerous here because the skill performs automatic saving, classification, and persistence of content once activated.
The activation instructions provide trigger phrases but do not define meaningful negative examples or guardrails, so the skill may activate on ambiguous conversational cues. Because activation leads to data capture and execution-oriented processing, mistaken invocation can expose private content and start workflows the user did not intend.
The instruction to save the full batch and read prior value-stack/meta-think files establishes persistent reuse of complete user-provided content across sessions without sensitivity boundaries. This creates a memory corpus of user inputs that can leak confidential information into later outputs or unauthorized files.
The batch doc format retains full prompt text and adds classifications and notes under each item, multiplying the number of places where sensitive user data can be copied. This propagation increases exposure, complicates deletion, and makes accidental reuse or disclosure more likely.
The skill continues processing automatically after 30 seconds of no response, which treats silence as consent. In a workflow that may execute prompts, perform research, and persist content, auto-continuation can cause unintended actions and additional data handling without renewed user approval.
The value stack, parked, discarded, and connection-graph files create durable aggregation of prior user content into reusable memory artifacts. Even if each individual note seems harmless, long-term accumulation can reconstruct sensitive projects, interests, strategies, or proprietary material across batches.
The skill claims to process prompt batches, but its behavior expands into persistent cross-batch memory management, value ranking, archival, and self-improvement. This scope expansion increases data retention and authority beyond what a user would reasonably expect from a batch executor, creating a hidden stateful system that can accumulate sensitive user content over time.
The trigger condition is broad enough to activate on common user language about Google Drive or folder processing, which can cause the skill to engage unintentionally in contexts the user did not clearly consent to. Because this skill is designed for bulk processing and downstream file inspection, ambiguous activation increases the chance of over-collection and unintended handling of sensitive data.
The instructions tell the agent to open Google Drive, enumerate all files, and inspect file contents without any user-facing warning, scope confirmation, or minimization controls. In a Drive context, this can expose sensitive personal, business, or regulated data and normalize broad inspection beyond what is necessary for the user's immediate task.
No suspicious patterns detected.