Back to skill

Security audit

Task Decomposer

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only task-planning skill that helps decompose engineering work and does not request hidden access, persistence, or unsafe execution.

Install this if you want a Chinese-language engineering decomposition workflow. Review generated task plans before handing work to agents, especially plans involving database migrations, auth configuration, API deletion endpoints, or updates to project documentation.

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
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • 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 (6)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · templates/crud-microservice.md (reported line 46)May include surrounding context.

  • GET /api/{entity}/{id} → 200 + 返回对象
  • GET /api/{entity}?page=0&size=10 → 200 + 分页列表
  • PUT /api/{entity}/{id} → 200 + 返回更新对象
  • DELETE /api/{entity}/{id} → 204
  • 缺少必填字段 → 400 + 具体字段名
  • jar tf 确认 class 文件存在
text

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The entire skill description, workflow, templates, and outputs are written as mandatory Chinese-language instructions, including prescribed artifact names like 需求拆解说明.md and 任务分配表.md. There is no indication that users may choose another language or that the Chinese-only constraint is required for a region-specific or compliance reason, which creates a natural-language locale policy concern.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This markdown file presents all operational instructions 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. Under the policy criteria, forcing a specific language without user opt-in is a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

该模板全文以中文标题和说明呈现,且未说明这是可选语言、特定区域要求,或允许用户选择其他语言。根据规则,若技能内容强制特定语言而没有用户选择或明确合理性说明,属于自然语言政策违规。

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

This markdown template is entirely written in Chinese, including headings, labels, and placeholders, and does not indicate that the user can choose another language. Under the policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale restriction is clearly documented and justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
93% confidence
Finding

This markdown template forces a specific language/locale for all users through its natural-language content. Under the policy, language constraints should either be optional, user-selectable, or clearly justified as region-specific.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.