ClawHub
Back to skill

Security audit

Alvis GitHub CLI

Security checks for vulnerabilities and agentic risk

Overview

This is a small GitHub CLI helper skill whose authenticated repository actions are disclosed and aligned with its purpose, though users should be deliberate before allowing write operations.

Install this only if you want the agent to use your existing GitHub CLI login. For write actions such as repo creation, issue comments, PR merges, and releases, explicitly provide the owner/repo and ask the agent to confirm the target before running the command. Treat the external setup-guide link as unreviewed remote documentation.

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

The skill description is broadly scoped to 'GitHub repos, PRs, or issues from the CLI,' which can cause the agent to invoke this skill for a wide range of generic GitHub-related requests without clear guardrails. Because the skill enables authenticated repository actions such as create, fork, merge, and release, overbroad triggering increases the chance of unintended or user-ambiguous execution against the wrong repository or with excessive privileges.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.