Back to skill

Security audit

qa-api-testing

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent API testing guidance skill with defensive QA content and no evidence of hidden execution, persistence, exfiltration, or destructive behavior.

Install this if you want Chinese-language API testing checklists and templates. Use any generated security, load, webhook, or retry tests only against systems you own or are explicitly authorized to test, especially where real credentials, payments, or write operations are involved.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The activation trigger includes an overly broad condition equivalent to 'when API testing is needed,' which can cause the skill to activate for loosely related requests. In an agentic system, over-broad routing can expose unnecessary tools, produce unintended security-testing guidance, or override a more appropriate safer skill, increasing the chance of misuse or policy drift.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The when-to-use field repeats the same broad activation logic without boundaries, reinforcing over-selection of this skill. In practice, duplicate broad triggers make misrouting more likely and can lead the agent to provide security-testing or exploitation-adjacent workflows in contexts where the user did not clearly request them.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The file title and all instructional content are written entirely in Chinese, which imposes a specific language on the skill's use. There is no visible opt-in, alternative language option, or justification that this skill is intentionally region- or locale-specific.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

The manifest description is primarily written in Chinese, with only a partial English sentence appended, and the rest of the skill content continues in Chinese. This can violate a language/locale policy if organizational guidance requires not forcing a language without user opt-in.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

SQP-3 applies to all file types and covers natural-language policy issues such as forcing a specific language without user opt-in. This markdown file presents all instructions and checklists only in Chinese, with no indication of optional language support or a justified region-specific scope.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.