Back to skill

Security audit

API Documentation Generator

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward API documentation generator with no executable code, persistence, credential handling, or hidden behavior found.

This appears safe to install for generating API documentation. When using it, review generated examples before publishing and avoid pasting secrets, credentials, or private production data in route files or controller snippets.

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

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 · README.md (reported line 29)May include surrounding context.

md
## Example

Tell your agent: "Document my user API: GET /users, POST /users, GET /users/:id, PUT /users/:id, DELETE /users/:id"

You'll get a complete OpenAPI spec, formatted reference docs, and integration quickstart — all consistent, all with realistic examples.

Static analysis

No suspicious patterns detected.