All 19 static findings are false positives caused by Markdown formatting and multilingual prose. The skill still directs active API and load testing without authorization or production safeguards. Add explicit consent, scope, rate, and environment checks before publication.
Eight static findings are confirmed because their cited ranges direct the agent to install dependencies or execute test, load, Python, and container commands. Eleven findings are false positives caused by Markdown backticks, code fences, tool names, or UTF-8 Chinese documentation rather than executable or obfuscated content. Active API and load testing also lacks explicit authorization and environment safeguards.
Missing Authorization Safeguards for Active Testing
The skill requires real API calls and load tests but does not require target ownership, explicit authorization, non-production confirmation, traffic limits, or stop conditions.
The cited workflows explicitly require actual API and performance test execution. The document contains no authorization or production-safety gate for those actions.
Capability review items (8)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The cited example directs the agent to run pip install and pytest. Installing project requirements and executing tests can run untrusted package or repository code without an approval boundary.
Line 172 explicitly chains pip install, Playwright installation, and pytest execution. Dependency installation and test execution modify the environment and can execute untrusted code.
The range instructs the agent to execute a generated Python API test and includes load-test commands. Generated scripts and supplied targets are not constrained by approval or isolation.
Line 174 provides direct k6 and wrk command invocations against a URL. These commands generate substantial traffic and can disrupt an unintended target.
The cited range includes direct pytest execution and a Docker Compose command. Both execute project-controlled configuration or code and can change the local environment.
Line 179 directs the agent to start services with Docker Compose. Repository-controlled compose files can run images, expose ports, mount files, and alter the host environment.
Eight static findings are confirmed because their cited ranges direct the agent to install dependencies or execute test, load, Python, and container commands. Eleven findings are false positives caused by Markdown backticks, code fences, tool names, or UTF-8 Chinese documentation rather than executable or obfuscated content. Active API and load testing also lacks explicit authorization and environment safeguards.
Missing Authorization Safeguards for Active Testing
The skill requires real API calls and load tests but does not require target ownership, explicit authorization, non-production confirmation, traffic limits, or stop conditions.
The cited workflows explicitly require actual API and performance test execution. The document contains no authorization or production-safety gate for those actions.
Capability review items (8)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The cited example directs the agent to run pip install and pytest. Installing project requirements and executing tests can run untrusted package or repository code without an approval boundary.
Line 172 explicitly chains pip install, Playwright installation, and pytest execution. Dependency installation and test execution modify the environment and can execute untrusted code.
The range instructs the agent to execute a generated Python API test and includes load-test commands. Generated scripts and supplied targets are not constrained by approval or isolation.
Line 174 provides direct k6 and wrk command invocations against a URL. These commands generate substantial traffic and can disrupt an unintended target.
The cited range includes direct pytest execution and a Docker Compose command. Both execute project-controlled configuration or code and can change the local environment.
Line 179 directs the agent to start services with Docker Compose. Repository-controlled compose files can run images, expose ports, mount files, and alter the host environment.
Eight static findings are confirmed because their cited ranges direct the agent to install dependencies or execute test, load, Python, and container commands. Eleven findings are false positives caused by Markdown backticks, code fences, tool names, or UTF-8 Chinese documentation rather than executable or obfuscated content. Active API and load testing also lacks explicit authorization and environment safeguards.
Missing Authorization Safeguards for Active Testing
The skill requires real API calls and load tests but does not require target ownership, explicit authorization, non-production confirmation, traffic limits, or stop conditions.
The cited workflows explicitly require actual API and performance test execution. The document contains no authorization or production-safety gate for those actions.
Capability review items (8)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The cited example directs the agent to run pip install and pytest. Installing project requirements and executing tests can run untrusted package or repository code without an approval boundary.
Line 172 explicitly chains pip install, Playwright installation, and pytest execution. Dependency installation and test execution modify the environment and can execute untrusted code.
The range instructs the agent to execute a generated Python API test and includes load-test commands. Generated scripts and supplied targets are not constrained by approval or isolation.
Line 174 provides direct k6 and wrk command invocations against a URL. These commands generate substantial traffic and can disrupt an unintended target.
The cited range includes direct pytest execution and a Docker Compose command. Both execute project-controlled configuration or code and can change the local environment.
Line 179 directs the agent to start services with Docker Compose. Repository-controlled compose files can run images, expose ports, mount files, and alter the host environment.