Back to skill

Security audit

QSR Food Cost Diagnostic

Security checks for vulnerabilities and agentic risk

Overview

This is a conversational restaurant food-cost diagnostic skill with disclosed, purpose-aligned tracking and no executable or privileged behavior.

Before installing, understand that the skill may retain food-cost percentages, targets, root causes, actions, and follow-up dates for pattern tracking. Use explicit commands when you want a diagnostic, and avoid entering sensitive business details you do not want stored in agent memory.

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 skill advertises activation by saying "food cost is high," which is a natural phrase an operator might use casually in discussion rather than as an intentional invocation. Because the document does not provide tighter trigger boundaries or negative examples, this could cause unintended activation during ordinary conversation about restaurant performance.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The trigger section says to run when food cost "feels off" or when pattern tracking shows an issue due for follow-up, but it does not clearly distinguish discussion signals from actual run commands. This ambiguity makes it unclear when the skill should activate versus when it should simply continue normal conversation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.