Security audit

Unit Test Coverage Helper

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only helper for unit-test and coverage workflows, with broad activation wording but no hidden execution, data access, persistence, or deceptive behavior.

Before installing, be aware that this skill may be invoked automatically for broad testing or quality-related prompts. It appears safe as a workflow aid, but users who prefer precise routing should invoke it explicitly for unit-test coverage tasks.

A.I.G

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

SkillSpector

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

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger sentence 'Help me ...' is extremely broad and resembles normal conversational language, so it can cause the skill to activate in contexts far beyond unit testing or coverage work. Over-broad activation increases the chance of unintended routing, context hijacking, or the skill being invoked on loosely related requests where its instructions may override a more appropriate specialization.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The invocation description is ambiguous because it maps a generic request for a 'practical workflow' onto this skill without clearly limiting scope to unit-test coverage activities. In agent systems, ambiguous trigger scope can cause accidental invocation, misclassification of user intent, and unnecessary exposure of the skill's instructions in unrelated conversations.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger phrases are broad enough to match ordinary requests about unit tests, test coverage, or practical workflows, which can cause the skill to activate more often than intended. Over-broad activation is risky because it can hijack unrelated conversations, reduce user control, and increase the chance that later skill instructions influence the agent in contexts where this skill was not explicitly requested.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The skill description is broad enough to match many ordinary software-help requests, which can cause the skill to activate outside its intended scope. Over-broad routing increases the chance of unintended instruction injection, incorrect tool selection, or interference with safer/more specific skills.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger keywords are highly generic terms commonly found in normal developer conversations. This makes accidental or excessive activation likely, which can misroute user requests and expand the attack surface for prompt or workflow abuse through inappropriate skill selection.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The skill description defines usage conditions too broadly, covering a wide range of software-and-data and testing-related requests without clear exclusion criteria. This ambiguity increases the chance of overbroad routing, where the skill is selected for tasks it was not designed to handle, reducing control over agent behavior and potentially interfering with more appropriate skills.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The trigger keywords are broad and include common software-development terms such as 'testing' and 'quality', which can overlap with routine conversations far beyond the skill’s intended scope. This can cause accidental invocation, leading the agent to apply an irrelevant workflow or expose users to unintended behavior through over-selection of the skill.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The skill description and default prompt are broad and repetitive, making it easier for orchestration logic to invoke the skill for loosely related requests such as general software help rather than narrowly scoped unit-test coverage tasks. In systems with implicit routing, this increases the chance of unintended activation, which can expose user context to the skill unnecessarily or cause the agent to take actions outside the user's intended scope.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: Enabling implicit invocation without well-defined trigger constraints allows the platform to auto-select this skill based on broad semantic similarity rather than explicit user intent. Because this skill is framed broadly around testing and software support, unintended invocation is plausible and may lead to unnecessary context sharing, confusing behavior, or execution of test-related workflows when the user did not request them.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger sentence is so broad and awkwardly templated that it can match ordinary requests about testing or practical workflows, causing the skill to activate outside its intended scope. Over-broad activation is dangerous because it can hijack unrelated user interactions, reduce routing precision, and make downstream behaviors less predictable, especially in environments where skills are auto-invoked from natural language.
Content: No source excerpt is available for this finding.

Vague Triggers

Low

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The example trigger uses everyday language that could match routine conversation rather than a deliberate request for this specific skill. While less severe than broad metadata or keyword triggers, it still reinforces permissive activation behavior and may cause ambiguous routing.
Content: No source excerpt is available for this finding.