T01 · Skill Instruction Hijacking
- Location
SKILL.md:24- Finding
Broad Skill Persona and Engagement Directives Hijack Agent Session Behavior
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This game skill has no clear malware or exfiltration, but it needs Review because it combines broad auto-activation, persistent player tracking, real-money monetization guidance, and weak virtual-economy controls.
Install only after deciding you explicitly want a persistent, engagement-optimized arcade. Disable or remove paid tournaments, prize pools, affiliate links, sponsorships, and real-money mappings unless you have platform, legal, age, consent, and disclosure controls. Keep Arcade Coins virtual-only until the state engine has authorization, validation, audit logs, and anti-abuse fixes. Operators should also add clear opt-in activation, data retention, and delete/export controls before deploying in group chats.
SKILL.md:24Broad Skill Persona and Engagement Directives Hijack Agent Session Behavior
scripts/arcade_engine.py:184Unrestricted Save Command Allows Arbitrary Player-State Modification
scripts/arcade_engine.py:418Unknown Achievement IDs Generate Unlimited Rewards
scripts/arcade_engine.py:518Self-Gifting Creates Virtual Currency Because Transfers Are Not Alias-Safe
The activation triggers are extremely broad, including generic phrases like 'I'm bored' and ambient group-chat cues, so the skill may activate without an unambiguous request. In context, that is more dangerous because the skill is explicitly designed to maximize engagement and retention, making accidental invocation likely to lead to spammy behavior, manipulative nudging, or unwanted state changes.
The skill includes monetization paths such as tipping, tournament entry fees, prize pools, and affiliate links despite being presented as an entertainment module. This increases financial, compliance, and abuse risk because an agent could pressure users into spending money or facilitate wagering-like flows without clear safeguards, eligibility checks, or operator controls.
The file introduces payment-gated gameplay, premium access, and psychologically manipulative retention prompts despite the metadata claiming zero cost. This is risky because it enables undisclosed financial transactions and pressure-based monetization in a context users and integrators may assume is free entertainment, creating deception, compliance, and consumer-protection exposure.
The documentation adds sponsored game rounds, branded themes, and advertising integrations that are absent from the stated entertainment scope. This is dangerous because covert ad delivery through gameplay can mislead users, especially if sponsorships are blended into normal game interactions without clear disclosure or policy review.
The playbook recommends contextual affiliate links and conversion tracking, which expands the skill into marketing and user-behavior optimization beyond its declared purpose. This creates risk of undisclosed commercial influence, tracking without clear consent, and misuse of gameplay context to drive purchases.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## Why Every Bot Needs This
- **Engagement** — Games keep users coming back daily
- **Retention** — Streaks, leaderboards, and achievements create stickiness
- **Virality** — "Beat my score" and shareable wins drive organic growth
- **Monetization** — 7 built-in revenue streams (see monetization playbook)
- **Zero cost** — Pure text/logic, runs locally, no external APIs
The README explicitly states the skill should also activate on broad conversational cues like boredom, celebration, or competitive banter, which can cause unintended invocation outside clear user requests. In a multi-skill agent, this increases the chance of context hijacking, user confusion, and accidental engagement flows being triggered when the user did not intend to play a game.
The skill instructs the agent to use a local Python script for persistent state while declaring no explicit tool scope or allowed-tools boundary. That creates an authority mismatch: a host may expose file, environment, or process capabilities that the skill can implicitly rely on without review, increasing the chance of unintended file access or unsafe execution paths.
The skill persistently stores player IDs, stats, streaks, achievements, and leaderboards but provides no notice, consent flow, retention policy, or deletion controls. In this context, the data collection is not essential to basic chat safety and could expose behavioral profiles or identifiers, especially in group settings where users may not expect long-term tracking.
The manifest advertises 'Zero dependencies' and 'Zero external APIs,' but the skill requires invoking python3 scripts/arcade_engine.py for core functionality. Even if not a network dependency, this is still an execution dependency and misleading capability disclosure can cause operators to trust and enable the skill without understanding it needs local code execution and persistent storage.
Prediction and competitive features use wagering-like mechanics, mention coins wagered, payouts, tips, and prize pools, but do not clearly warn users about monetization or financial implications. In an entertainment skill optimized for engagement, these mechanics can normalize gambling-adjacent behavior and blur the line between virtual play and real-money pressure.
This section explicitly documents persuasive design techniques such as variable-ratio reinforcement, loss aversion, sunk cost, and peak-end optimization to increase retention and repeated play, but does not pair them with safeguards, consent, age-appropriate limits, or wellbeing disclosures. In an entertainment skill aimed at boredom relief, group play, and ongoing engagement, these mechanics can encourage compulsive use and exploit vulnerable users, especially minors or users prone to problematic gaming behavior.
The documentation explicitly frames the skill as a revenue-generation system, which materially exceeds the manifest's entertainment-only description. This scope mismatch is dangerous because downstream users, reviewers, or platforms may enable the skill believing it is harmless game content while it actually steers operators toward monetization features and growth tactics.
The sponsored-content and affiliate sections discuss monetization tactics but do not require strong user-facing disclosures that content is paid promotion or that links generate commissions. This is dangerous because users may not realize game content is advertising, creating deception, trust erosion, and regulatory risk around endorsement transparency.
Referral growth incentives and affiliate monetization are not justified by the skill's stated purpose as a simple entertainment engine and introduce commercial propagation behavior. In this context, game achievements are being used to drive recruitment and purchases, increasing the chance of spammy growth loops and deceptive commercialization.