Back to skill

Security audit

dev-test

Security checks for vulnerabilities and agentic risk

Overview

This is a generic development-and-testing workflow skill with broad activation wording but no hidden code, persistence, credential handling, or unsafe automation.

Install this if you want a general disciplined workflow for coding tasks. Be aware it may activate often because its description is broad; for specialized work such as security reviews, deployments, or repo-specific release processes, prefer a more specific skill or project instructions.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The description is extremely broad ("applies to any development work"), which can cause the skill to activate for a large share of ordinary coding requests. Over-broad activation increases the chance the agent follows this workflow in inappropriate contexts, potentially overshadowing more specific or safer skills and expanding the blast radius of any bad guidance embedded in the skill.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The use-case section lists very broad categories (bug fixes, features, refactors, open-source contributions, any code change) but does not define boundaries for when the skill should not be used. That ambiguity can make routing overly permissive, causing the SOP to be applied to requests outside its intended scope and reducing control over tool/skill selection.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.