ClawHub
Back to skill

Security audit

GitHub PR Writer

Security checks for vulnerabilities and agentic risk

Overview

This skill drafts pull request descriptions from repository context and does not show hidden execution, persistence, destructive actions, or data exfiltration.

Before installing, understand that the skill may inspect your current branch diff and commit history to draft PR text. Review the generated PR description before sharing it, especially in private repositories, but the inspected artifacts do not show hidden or unsafe behavior.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill advertises several broad trigger phrases such as 'create a PR', 'open a pull request', and activation when 'a branch is ready to merge', which can cause it to be invoked in contexts where the user did not explicitly request this specific skill. Unintended activation can lead to unnecessary repository inspection commands and generation of PR content from the current branch context, creating confusion or accidental disclosure of code-change details into the wrong workflow.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.