Back to skill

Security audit

performance-monitor

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only performance monitoring skill whose behavior fits its stated purpose, with caution needed before applying real infrastructure changes.

Install only if you want an agent to help with observability and performance monitoring. Before allowing it to change a real environment, confirm the target systems, telemetry sensitivity, collector overhead, alert destinations, integrations, and rollback plan.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill's invocation guidance is extremely broad and effectively allows activation for any performance-related context without clear trigger boundaries, scope limits, or disambiguation rules. In a multi-agent environment, this can cause inappropriate activation, overreach into unrelated tasks, or autonomous monitoring actions being proposed or taken where the user did not explicitly request them.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The implementation phase instructs the agent to install collectors, configure aggregation, set up alerts, and enable integrations without any safety gate, change-control step, or warning about operational impact. In this context, that is dangerous because monitoring changes can alter production systems, increase load, introduce security/privacy exposure through telemetry collection, and create unauthorized infrastructure modifications.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.