Back to skill

Security audit

Operator Hardening Pack

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only workflow for organizing agent setup hardening and task handoffs, with no bundled code, network behavior, or hidden execution.

Install this only if you want an agent workflow that may review and adjust workspace instruction or memory files. Check proposed memory or agent-guidance changes before accepting them, especially in shared or production repositories.

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

The phrase 'Use this skill as the top-level entry point when you need a reliable, safety-first agent operating system' is an open-ended activation description without concrete scope boundaries or exclusion conditions. This could cause the skill to be invoked for a wide range of ordinary agent tasks rather than a narrowly defined scenario.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

Conditions such as 'Existing workspace feels inconsistent/noisy' and 'Complex multi-step tasks with quality drift' rely on subjective judgment and do not clearly distinguish activation from non-activation cases. The absence of explicit thresholds or examples increases the chance of unintended or inconsistent invocation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.