Back to skill

Security audit

software-spec-writing

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation workflow skill that writes project spec files and coverage metadata, with no hidden execution, credential use, network retrieval, or system persistence found.

Install this if you want a strict Traditional Chinese workflow for maintaining software specs and coverage files. Expect it to steer documentation structure strongly and to pause feature coding when required FR/AC entries are missing.

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

Natural-Language Policy Violations

High
Category
Not specified by scanner
Confidence
88% confidence
Finding

The skill mandates a specific output format choice without user opt-in, which can conflict with user preferences or project conventions and reduce agent reliability. While this is not a direct security exploit, it is a policy-overreach pattern that can cause unexpected behavior and make downstream interactions harder to control.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill's activation criteria are extremely broad, triggering on common terms like 'spec', 'document', 'coverage', or even when code is about to be written without an obvious spec. This can cause the skill to activate in many unrelated contexts, effectively overriding normal task routing and steering the agent into this workflow when the user did not clearly request it.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This markdown file is written entirely in Traditional Chinese and does not indicate that language choice is optional or limited to a justified region-specific context. Under the policy rule for natural-language violations, forcing a specific language without user opt-in is in scope.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The title and the entire document prescribe writing conventions in Traditional Chinese, but there is no indication that users may choose another language or that the constraint is limited to a region-specific context. This creates a natural-language locale policy issue because the skill appears to force a specific language without opt-in.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

This markdown file contains user-facing instructions exclusively in Chinese, and nowhere indicates that the user may choose another language or that the skill is intentionally limited to a Chinese-speaking context. Under the language/locale policy rule, forcing a specific language without 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
89% confidence
Finding

This markdown file presents the skill documentation entirely in Traditional Chinese and frames it as the default reference for team members, but does not offer any language choice or indicate that Chinese is an explicit user-selected or region-specific requirement. Under the policy, forcing a specific language without opt-in is a natural-language locale violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

This manifest/template contains user-facing instructional text exclusively in Traditional Chinese, including operational rules and status definitions. The file does not indicate that language selection is optional or justified as a region-specific requirement, which can violate the language/locale policy for natural-language content.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.