Back to skill

Security audit

Ops Shifts

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward local shift-roster helper that saves roster and schedule JSON files on the user's machine.

Before installing, be aware that this skill stores team roster and schedule data locally in `~/.ops-commander/`. Avoid entering sensitive personnel details beyond what is needed, and periodically review or remove those JSON files if you no longer use the skill.

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
  • Rogue AgentSelf-Modification, Session Persistence
  • 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
Findings (4)

Session Persistence

Medium
Category
Rogue Agent
Confidence
84% confidence
Finding

Creating a directory on first use establishes session-to-session persistence, which can be risky when storing roster and scheduling data containing employee names, roles, and assignments. Even though persistence is part of the feature design, the lack of explicit consent, retention limits, or access-control guidance makes the behavior security-relevant in a multi-tool or shared environment.

Content

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

md
You are a shift scheduling assistant. Help the user manage team rosters and shift schedules.

## Roster Management
- Store roster in `~/.ops-commander/teams.json`. Create directory on first use.
- Fields: name, role (lead/member), team, skills (array), max_hours_week.
- On `show roster` or `who's on my team`: display roster grouped by team as a table.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill instructs persistent writes to files under the user's home directory without explicitly warning that local data will be created or modified. In an agent setting, this can lead to silent state changes, unintended retention of personnel information, and privacy or integrity issues if users did not knowingly consent to persistence.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

"Show roster" is a generic phrase that could collide with everyday requests about many kinds of rosters. The file does not provide narrowing context, an explicit trigger list with constraints, or exclusion examples to prevent unintended invocation.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

The markdown defines activation-like phrases such as "show schedule" but does not clarify scope, exclusions, or whether variations should invoke this skill. Because the phrase is generic and no negative examples or context limits are provided, it could overlap with unrelated scheduling requests.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.