Back to skill

Security audit

Openapi Docs Generator

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-focused OpenAPI/Swagger helper with broad routing language but no hidden execution, persistence, credential access, or destructive behavior.

Installers should be aware that this skill may activate on general OpenAPI, Swagger, REST API, or developer-experience prompts. It is otherwise a plain documentation workflow skill, so review outputs as normal and invoke it explicitly when you want OpenAPI documentation help.

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

Vague Triggers

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The trigger sentence begins with a broad, everyday phrase ('Help me ...'), which can cause the skill to activate on generic user requests that are only loosely related to OpenAPI documentation. Over-broad activation increases the chance of unintended routing, where unrelated prompts are handled by this skill and inherit its assumptions or workflows without clear user intent.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger phrases are generic and structurally broad enough that normal user requests about OpenAPI, Swagger, or API documentation could invoke the skill unintentionally. This increases the chance of misrouting user prompts, causing the agent to apply this skill in contexts where it was not explicitly requested and potentially exposing users to incorrect workflows or unintended tool behavior.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger phrases are broad, repetitive, and loosely scoped, which can cause the skill to activate for generic OpenAPI or API-documentation requests without clear user intent. In an agent environment, unintended invocation can route prompts into the wrong workflow, increasing the chance of inappropriate actions, irrelevant outputs, or prompt-surface expansion across unrelated requests.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill description is broad enough that it may activate for generic software, API, or documentation requests that do not specifically require this skill. Over-broad activation can cause inappropriate routing, making the agent apply the wrong workflow or expose users to unnecessary file inspection or code-generation behavior in unrelated contexts.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger keywords are generic terms like 'openapi', 'swagger', and 'rest api' without disambiguation, so the skill may be invoked on incidental mentions instead of genuine documentation tasks. In an agent system, this increases misrouting risk and can crowd out more appropriate skills, reducing reliability and potentially causing unintended processing of user content.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill description uses broad topical terms like software-and-data, openapi, swagger, api documentation, and rest api without meaningful scope limits or exclusion criteria. This can cause the skill to activate during ordinary technical conversations that merely mention these terms, leading to unintended routing, irrelevant instructions, or context hijacking of the user’s request.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger keyword list is overly broad and lacks disambiguation rules, so commonplace terms like openapi, swagger, rest api, and developer experience may match many unrelated requests. In an agent system, ambiguous triggers increase the chance of accidental invocation, which can misroute tasks, override more appropriate skills, or inject an unnecessary workflow into benign conversations.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The default prompt uses broad natural-language phrasing such as helping with OpenAPI/Swagger/API documentation in general, which increases the chance of accidental activation from common developer queries. In combination with implicit invocation, this can cause overbroad routing and unintended execution of the skill in contexts the user did not explicitly request.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill enables implicit invocation but does not define narrow trigger constraints in this file. That creates a prompt-routing risk where ordinary user requests about APIs or documentation could automatically invoke the skill unexpectedly, expanding the attack surface and allowing unintended handling of user inputs or context.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The phrase 'I need a practical workflow for ...' is vague and does not clearly constrain the skill to OpenAPI or Swagger tasks, making accidental invocation more likely. In an agent environment, ambiguous triggering can cause misrouting, irrelevant disclosures, or inappropriate execution paths when the user intended a different workflow-oriented skill.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
71% confidence
Finding

This is a Chinese-language README, but substantial user-facing content including the title, demand description, and trigger phrases is presented only in English. The document does not state that English is required nor offer an explicit language choice, which can impose a locale preference without opt-in.

Content

No source excerpt is available for this finding.