ClawHub
Back to skill

Security audit

TDD Workflow

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only TDD workflow skill whose test-running and git-checkpoint guidance matches its stated purpose.

Install this if you want an agent to follow a stricter TDD workflow. Be aware it encourages running project tests and making local git checkpoint commits, so review those commits before sharing or pushing them.

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
95% confidence
Finding

The description says to use the skill when 'writing features, fixing bugs, or refactoring' and includes trigger phrases like 'feature implementation' and 'bug fix'. These are common software-development activities and phrases that could match many routine requests, but the file does not clearly define constraints or exclusion conditions for when the skill should not activate.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The activation list includes phrases such as 'write tests' and 'how should I test this', which are broad enough to overlap with ordinary conversation or ad hoc coding help. The document does not provide negative examples or other boundaries to distinguish simple testing questions from invocation of the full TDD workflow skill.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.