ClawHub
Back to skill

Security audit

safe-git-push

Security checks for vulnerabilities and agentic risk

Overview

This is a guidance-only skill for safely publishing selected workspace files to a Git remote, with clear warnings to avoid accidentally uploading secrets or unrelated files.

Before using this skill, confirm the exact project directory, repository visibility, and final staged file list. The fallback GitHub Contents API path uploads selected files using the active gh credentials, so review for secrets such as .env files, keys, tokens, and unrelated workspace folders before running it.

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)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The manifest description is written entirely in Chinese and defines triggers using Chinese phrases only, which implies a language-specific activation policy. There is no indication that other languages are supported or that the user can opt into this locale restriction.

Content

No source excerpt is available for this finding.

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical
Code
suspicious.exposed_secret_literal
Location
SKILL.md:120