Back to skill

Security audit

Legal Due Diligence Checklist

Security checks for vulnerabilities and agentic risk

Overview

This is a document-only legal due diligence checklist skill with clear legal disclaimers and no executable or hidden behavior.

Installers should treat this as an informational legal workflow aid only. Do not rely on it as legal advice, and verify jurisdiction-specific requirements, deadlines, confidentiality duties, and transaction strategy with qualified counsel.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The acceptance criteria state that SKILL.md and README.md are "English-first," which imposes a language preference as a policy requirement. Under the policy rules, forcing a specific language without user choice or clear region-specific justification 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
95% confidence
Finding

The package rules explicitly require the package to remain "English-first," which is a language policy constraint. Because no opt-in, alternative language support, or justified locale limitation is provided, this conflicts with the stated natural-language policy requirements.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The manifest header sets language: en and the acceptance criteria state the markdown should be English-first, but Scenario 4 is written entirely in Chinese. This creates a language/locale inconsistency without user opt-in or an explicit multilingual policy, which fits the language-policy violation category.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
94% confidence
Finding

The manifest sets "language": "en", which is a natural-language locale constraint. The file does not indicate that users can opt into another language or that the English-only behavior is required for a region-specific or otherwise justified purpose.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.