Back to skill

Security audit

predictive-maintenance-engineer

Security checks for vulnerabilities and agentic risk

Overview

This skill is a markdown-only reliability guide whose automation advice is relevant to its purpose, but users should treat operational changes as advisory and approval-gated.

Installers should treat this as an advisory reliability playbook. Before using its recommendations to restart services, clean files, renew certificates, or remove instances from load balancers, require operator approval, confirm environment scope, validate backups or rollback options, and follow existing change controls.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill explicitly recommends auto-remediation actions such as restarting services, cleaning files, auto-renewing certificates, and removing instances from load balancers, but it does not consistently frame these as requiring operator confirmation, change controls, rollback plans, or environment-specific safeguards. In an agent context, prescriptive automation guidance can be treated as approval to take disruptive actions, which may cause outages, data loss, or unsafe remediation if applied blindly.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.