Back to skill

Security audit

Token Budget Advisor

Security checks for vulnerabilities and agentic risk

Overview

This skill only changes how the agent asks about and controls answer length, with no code execution, data access, network use, or hidden persistence.

Before installing, understand that this skill may ask you to choose answer depth when you use common words like brief or detailed; it does not appear to access private data or run code.

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

The manifest description lists triggers such as "short version," "brief answer," and "detailed answer," which are common conversational phrases that could appear in many contexts unrelated to this skill. Because these phrases are broad and the manifest does not tightly constrain invocation context there, the skill risks unintended activation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The guidance says to use the skill when a user mentions "tokens, budget, depth, or response length" or says terms like "brief" and "exhaustive," but these conditions are broad and could match ordinary requests. Although there is one exclusion at L17, the file still lacks sufficiently specific constraints or negative examples to reliably separate intentional activation from normal conversation.

Content

No source excerpt is available for this finding.