Back to skill

Security audit

Design Gate

Security checks for vulnerabilities and agentic risk

Overview

This skill is a local design-review checker with no evidence of hidden data access, network use, or automatic persistence.

Install only if you want a lightweight local checker for structured design documents. Review its scoring rules before relying on pass/fail decisions, because they are simple heuristics rather than a full architecture review.

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
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (3)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The skill is described in very broad terms as a generic design gate checker with multiple use cases and no clear trigger boundaries, exclusions, or least-privilege constraints. Overly generic invocation criteria can cause the agent to apply the skill in unintended contexts, increasing the chance of inappropriate activation, overreach, or misuse alongside whatever tools the implementation may expose.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

This code includes natural-language string literals exclusively in Chinese for titles, descriptions, and component names. Under the policy, forcing a specific language without opt-in or documenting a justified locale-specific scope can be a language/locale policy violation, and no such justification appears in this file.

Content

No source excerpt is available for this finding.