Security audit

Github

Security checks for vulnerabilities and agentic risk

Overview

ClawScan marked this skill suspicious because it may publish a session URL in a pull request without warning the user; the scan was partial, so its evidence is incomplete.

Review the session-link disclosure concern before installing, especially if pull requests may be public or widely accessible. The scan was partial because a referenced local path could not be resolved; treat the findings as incomplete, not as assurance that no other issues exist.

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

Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
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)

The skill instructs the agent to publish a session URL in PR bodies without warning the user about that disclosure.

Medium

Category: Output Handling
Confidence: 94% confidence
Finding: The skill automatically copies a runtime-provided session URL into a PR body without requiring approval or checking whether the session is appropriate for the repository's audience. This crosses a disclosure boundary: a public or broadly accessible PR could expose an internal session identifier or link, and potentially session contents if the destination permits access. Requiring an existing exact URL reduces fabrication risk but does not establish authorization to publish it.
Content: No source excerpt is available for this finding.