ClawHub
Back to skill

Security audit

dev-workflow

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward development workflow checklist that asks the agent to use branches, confirm requirements, test changes, and wait for user approval before release.

Install this if you want a Chinese-language development workflow checklist that enforces branch-based work, requirement clarification, tests, and user acceptance before release. Be aware it may activate broadly for most coding tasks and may slow quick edits because it asks for process steps first.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The description and body say the skill must be invoked whenever a new development task or bug-fix task is received, which is a very broad trigger that overlaps with common day-to-day engineering work. The file does not provide narrowing constraints, explicit trigger phrases, or exclusion examples to clarify when the skill should not activate.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
81% confidence
Finding

All user-facing instructions in this skill are written in Chinese, and the skill does not state that the locale is optional, user-selected, or required for a justified region-specific context. This can create a language-policy issue if users are expected to interact in a forced language without opt-in.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.