Back to skill

Security audit

发布写作

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent release-management writing guide; its GitHub and git actions are disclosed and fit that purpose.

Install this if you want an opinionated release-writing workflow for repositories. Before using its commands, confirm the target owner, repo, version, branch, and GitHub authentication context, because the workflow can publish tags/releases and edit existing release notes.

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

The description says to use this skill when someone says phrases like “发个 release”, “整理 CHANGELOG”, and “把往期发布说明改一下”. Several of these are common, high-level requests without explicit scope limits or exclusion conditions, so the activation boundary is not precise enough for a manifest-style trigger description.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

The text mandates that section headings must be in English and that body language must follow the repository README's main language. This is a natural-language locale policy constraint presented as a rule, without offering a user choice or opt-in mechanism.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.