Back to skill

Security audit

Omni Tools

Security checks for vulnerabilities and agentic risk

Overview

This is a static reference skill that prints documentation and does not show credential access, network use, persistence, or destructive behavior.

This appears safe to install as a reference-only skill. Users should be aware that its command names are generic and may benefit from clearer namespacing, but the inspected artifacts do not perform sensitive actions.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • 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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · scripts/script.sh (reported line 64)May include surrounding context.

sh
## Prerequisites
- Basic understanding of devtools concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation

Vague Triggers

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

The skill lists very generic command words such as intro, patterns, security, and migration without stating the required invocation context or any exclusion conditions. In a markdown skill description, these broad terms can create ambiguity about when the skill should activate versus ordinary discussion of those topics.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.