ClawHub
Back to skill

Security audit

Ward Public Release Gate

Security checks for vulnerabilities and agentic risk

Overview

This is a release-review checklist skill with one minor scope conflict around creating a repo config file, but no hidden execution, exfiltration, persistence, or unsafe release automation.

Before installing, be aware that this skill may suggest adding a release-gate.config.json file when release automation is missing. Treat that as a separate change requiring your approval; the review workflow itself is otherwise framed as read-only and should not create tags, releases, uploads, deployments, or production changes without explicit permission.

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
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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)

Description-Behavior Mismatch

Medium
Confidence
90% confidence
Finding
The skill explicitly says the review should remain read-only by default, but later instructs the operator to create a new `release-gate.config.json` when automation is absent. That introduces a state-changing action during what is framed as a review-only gate, which can modify the repository, affect release behavior, and blur the boundary between assessment and implementation.

Static analysis

No suspicious patterns detected.