Back to skill

Security audit

Analytics

Security checks for vulnerabilities and agentic risk

Overview

This is a product analytics guidance skill whose tracking examples are expected for its purpose, with privacy considerations users should still review before implementation.

Before installing or using this skill to add tracking, confirm what data will be sent to analytics providers, avoid unnecessary personal data, use pseudonymous identifiers where possible, and make sure consent, privacy notices, and retention rules match your product and jurisdiction.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Confidence
96% confidence
Finding
The invocation description includes broad terms like "measure" and especially "or any task related to measuring product performance and user behavior," which lacks clear scope boundaries. This can cause the skill to activate for many general product or business discussions beyond a narrowly defined analytics request.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The skill provides concrete analytics instrumentation code, including event capture and user identification, without an explicit warning that this may collect and transmit user or behavioral data to a third-party analytics service. In agent contexts, this can normalize adding tracking code without informed consent, data minimization, or jurisdiction-specific compliance checks, increasing privacy and compliance risk.

Static analysis

No suspicious patterns detected.