Back to skill

Security audit

QSR Labor Leak Auditor

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed restaurant labor-tracking assistant that stores store-scoped business metrics but does not show hidden execution, exfiltration, or unsafe automation.

Install only if you are comfortable storing store-level sales, labor cost, weekly goal, and audit context in the configured store memory engine. Review the memory engine's retention, deletion, authentication, and access controls because this skill relies on that component for persistence and hard deletion.

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)

Skill Enumeration

Medium
Category
Agent Snooping
Confidence
85% confidence
Finding

Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Content

Scanner excerpt · SKILL.md (reported line 75)May include surrounding context.

md
Every record is tagged with a single store identifier and lives inside that store's namespace. Records never cross store boundaries. In multi-location deployments, each store has its own isolated labor history, goal tracker, and audit log. Cross-store rollups (see `ADAPTING THIS SKILL → Multi-location`) are produced by reading each store's namespace independently and combining the results at report time, not by merging the underlying records.

### Sibling skill access

Other skills in the QSR Operations Suite may read from this skill's records *only* through the same store-scoped namespace and *only* in read-only mode. Sibling skills do not modify, delete, or re-export labor or goal records.

Static analysis

No suspicious patterns detected.