Back to skill

Security audit

Open Source Analysis

Security checks for vulnerabilities and agentic risk

Overview

This skill is a read-only GitHub repository analysis helper with disclosed use of GitHub search/API access.

Installers should be comfortable with the skill making read-only GitHub lookups and optionally using existing GitHub authentication for higher API limits. Avoid using it for ambiguous project names unless you confirm the intended repository.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill’s trigger condition is broad enough to activate on generic requests about analyzing projects, which can cause unintended invocation outside a narrowly defined GitHub-repository-analysis context. This increases the chance of over-collection, confusion about scope, and accidental handling of unrelated user requests or untrusted external content without explicit user intent.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The expected output explicitly requires 'An English analysis report', which encodes a language constraint in natural-language content. Under the policy, forcing a specific language without user opt-in or a clearly documented regional justification is a violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

This line requires a Chinese report and additionally states 'NO English headings should be present,' which is a strict locale/language constraint. The file does not provide a documented justification for this enforced language policy beyond the test case itself.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The phrase 'The structure should strictly follow the English template' mandates a specific language/template choice in natural-language content. Because no opt-in or explicit justification is present, this matches the language/locale policy violation criteria.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.