Security audit

WBS Planner

Security checks for vulnerabilities and agentic risk

Overview

This skill is a project-planning guide that creates and manages roadmap, epic, and task documents, with no hidden code execution or persistence behavior found.

Install this if you want a Chinese-language WBS planning workflow for roadmap, epic, and task documents. Review actions that write or clear TASK.md, update roadmap files, or notify other agent sessions so those changes match your project process.

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

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

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The manifest description lists generic trigger terms such as "roadmap", "epic", "task breakdown", and "project planning" without clear scope constraints or exclusion examples. These phrases are broad enough to overlap with ordinary project discussion, making activation conditions ambiguous.

Natural-Language Policy Violations

Medium

Confidence: 97% confidence
Finding: The user-facing skill documentation is written in Chinese while the manifest and likely surrounding tooling context are not, effectively imposing a language choice without offering the user an explicit language or locale option. This can violate language/locale policy when no opt-in or justification is provided.

Natural-Language Policy Violations

Medium

Confidence: 95% confidence
Finding: This markdown guidance is entirely presented in Chinese and does not indicate that the user can select another language or that the skill is intentionally limited to a Chinese-speaking audience. That creates a natural-language policy concern under the language/locale rule because the skill effectively forces a specific language without user opt-in.

Natural-Language Policy Violations

Medium

Confidence: 95% confidence
Finding: This markdown file appears to prescribe a workflow entirely in Chinese, including headings, instructions, and log formats, with no indication that users may choose another language. Under the policy rule for natural-language violations, forcing a specific language without user opt-in is a reportable issue.

Natural-Language Policy Violations

Medium

Confidence: 92% confidence
Finding: The document presents all operational guidance exclusively in Chinese, and there is no indication that users may choose another language or that the skill is intentionally limited to a Chinese-speaking context. This can violate a language/locale policy when a skill implicitly forces one language without user opt-in.

Natural-Language Policy Violations

Low

Confidence: 92% confidence
Finding: The roadmap template is written entirely in Chinese, including headings, placeholders, and status labels, with no indication that users may choose another language. This can violate language/locale policy when a skill implicitly enforces a specific language without user opt-in or documented regional scope.

Natural-Language Policy Violations

Low

Confidence: 88% confidence
Finding: The template uses Chinese field labels and section headings throughout, such as '名称', '所属 Epic', '状态', and '执行记录', with no indication that the user may choose another language. This can violate language/locale policy when a skill imposes a specific language by default without documented opt-in or justification.

Static analysis

No suspicious patterns detected.