Back to skill

Security audit

release-health-gates

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only release checklist, but its broad triggers and instructions to update GitHub/tracker release records warrant user review before installation.

Install only if you want this skill to influence release-readiness workflows, and prefer explicit invocation or narrower triggers. Review any GitHub or tracker writes before applying them, especially task status changes, PR comments, approvals, waivers, and retrospective records.

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)

Shadow Command Trigger

Medium
Category
Trigger Abuse
Confidence
88% confidence
Finding

Using 'release' as a trigger conflicts with a built-in command of the same name, creating a shadowing risk where the skill may intercept or alter expected command behavior. In a deployment context, this can confuse operators, cause incorrect workflow execution, or apply the wrong guidance during a sensitive production release process.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The manifest declares very broad triggers such as 'release', 'github', 'readiness', 'quality', and 'governance', which are common terms likely to appear in many unrelated user requests. This increases the chance of unintended invocation, causing the skill to influence workflows or inject release-gating behavior when the user did not explicitly request it.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.