Open Source Release

• Outcome: Review
• Latest audit: Sep 11, 2026 · 2:10 AM UTC
• Version: 1.1.0

Overview

The skill fits its stated open-source release purpose, but it includes high-impact GitHub commands like force-pushing, deleting a branch, and making a repository public without a clear confirmation gate.

Only use this skill when you intentionally want an agent to prepare and publish a repository. Before running the destructive steps, verify the GitHub owner, repo, remote URL, current branch, backup state, and exact diff/history to be published; require explicit approval before any force push, branch deletion, or visibility change.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Tool Misuse: Tool Parameter Abuse, Chaining Abuse, Unsafe Defaults
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Hidden Instructions

High

• Category: Prompt Injection
• Confidence: 60% confidence

Finding

Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 1)May include surrounding context.

md

---
name: opensource-release
description: Convert a private repository to public open-source. Use when making a repo public, sanitizing personal info from code/docs/git history, or preparing a project for open-source release. Triggers on "open source", "make public", "public release", "sanitize repo".
---

Tool Parameter Abuse

High

• Category: Tool Misuse
• Confidence: 90% confidence

Finding

The skill instructs use of a force push when rewriting repository history during a public-release workflow. Even if well-intentioned, git push origin main --force is a dangerous parameter because an agent executing it automatically could overwrite remote history, destroy collaborators' work, or publish an unintended branch state, especially when combined with branch renaming and deletion.

Content

Scanner excerpt · SKILL.md (reported line 67)May include surrounding context.

git commit -m "feat: initial public release" git remote set-url origin https://github.com/{owner}/{repo}.git # verify no token in URL! git branch -M main git push origin main --force git push origin --delete {old-branch}

text

Static analysis

No suspicious patterns detected.