Security audit

Universal Release

Security checks for vulnerabilities and agentic risk

Overview

This release helper is mostly coherent, but it can turn a simple push request into local release edits, commits, tags, and possible remote publishing.

Install only if you want an opinionated release workflow. Do not use it for routine git pushes unless you are comfortable with it preparing a release; review planned file edits, commits, tags, target branch, and push behavior before allowing it to proceed.

A.I.G

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

Findings (1)

T01 · Skill Instruction Hijacking

Error

Location: SKILL.md:469
Finding: Explicit User Intent Overridden by Forced Release Workflow
Content: View full analysis
Remediation: View remediation

SkillSpector

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 (3)

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The skill metadata advertises very broad trigger phrases including generic terms like "push", "release", and multilingual variants, which can cause the release workflow to activate in contexts where the user did not intend a versioning and git/tagging operation. Because this skill performs high-impact repository actions such as committing, tagging, and potentially pushing to remote, accidental invocation materially increases the risk of unintended source-control changes.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The "When to Use" section explicitly instructs invocation on broad phrases like "push to remote" and even says to still follow the full release workflow when the user says "just push." This creates an unsafe semantic mismatch where a simple push request can trigger commits, changelog edits, version bumps, tagging, and remote publication that exceed the user's likely intent.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 87% confidence
Finding: The instructions require generating content in each detected changelog language and writing change descriptions naturally in that language. This imposes language output behavior based on file detection rather than explicit user choice, which can violate language/locale choice expectations.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.