Back to skill

Security audit

Skillhub Preference

Security checks for vulnerabilities and agentic risk

Overview

This is a small Markdown-only skill that openly tells the agent to prefer one skill registry before falling back to another, with no hidden code or persistence.

Before installing, be aware that this skill biases future skill search/install/update workflows toward skillhub first. That preference is disclosed, but users who want neutral registry selection may not want this behavior enabled by default.

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
93% confidence
Finding

The trigger description is broad enough to activate on generic requests about skills, plugins, or capability extension, which can cause this policy skill to be injected into unrelated conversations. Over-broad activation increases the chance of unintended tool-selection influence and can steer the agent toward registry operations when the user did not explicitly request discovery or installation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill states it should be used whenever the task involves skill discovery, installation, or upgrades, but it does not define exclusion conditions or precedence with other skills. This ambiguity can make the skill apply too often, influencing command execution policy and registry preference in contexts where another safer or more specific workflow should control behavior.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.