Back to skill

Security audit

Github Installer Agent

Security checks for vulnerabilities and agentic risk

Overview

The skill mostly does what it claims, but its “safe” clone script can delete any existing user-supplied target directory and includes a documented bypass for safety checks.

Review this before installing. Use only disposable or clearly dedicated target directories, avoid --no-check, do not rely on its validation scripts as proof of security, and manually inspect any dependency commands or third-party package mirror recommendations before running them.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (3)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/safe_clone.sh:129
Finding

Arbitrary Recursive Deletion Through an Unrestricted Target Directory

Content
View full analysis
/dev/null; then ``` The comments and messages above are translated into English for reporting; the executable statements are unchanged. ### Technical Analysis The script accepts `target_dir` as a command-line argument and passes it directly to: ```bash rm -rf "$target_dir" ``` Quoting prevents shell word splitting and command substitution, but it does not make the selected path safe. The script does not: - Resolve the path to its canonical location. - Reject `/`, the user's home directory, or another sensitive location. - Reject parent-directory traversal components such as `..`. - Restrict clones to a dedicated destination root. - Verify that the directory was previously created by this tool. - Reject a symbolic-link-based destination. - Verify that the directory is empty or contains only expected clone data. The interactive confirmation reduces accidental exploitation but is not an adequate authorization boundary. A user can misunderstand the prompt, and an automated agent, wrapper, or scripted input can approve it. ### Attack Path 1. An attacker influences the target directory supplied to the skill, or a user accidentally supplies a sensitive existing directory: ```bash ./scripts/safe_clone.sh https://github.com/example/repository "$HOME/Documents" ``` 2. The URL passes GitHub URL validation. 3. The script detects that the selected ta ...[truncated 883 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/validate_skill.sh:35
Finding

Security Validation Reports Hard-Coded Results Instead of Measuring Failures

Content
View full analysis
Remediation
View remediation
0 )); then exit 1 fi ``` 5. Remove assertions that cannot be tested. For example, do not report rate limiting as present unless the implementation actually enforces it. 6. Add behavioral tests instead of relying only on string searches. Required cases should include: - Dangerous target directories. - Invalid and ambiguous URLs. - Invalid clone depths. - GitHub API errors and malformed responses. - Existing directories and symbolic links. - Oversized repositories. 7. Have CI consume the script's exit status and block publication on failure. ]]>

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/test_security.sh:30
Finding

Security Test Script Produces an Unconditional Success Verdict

Content
View full analysis
/dev/null | grep -v "test_security.sh" | grep -v "#.*$pattern"; then echo "❌ Dangerous pattern found: $pattern" safe=false fi done if $safe; then echo "✅ No dangerous commands found" fi ``` However, the script later prints a successful final verdict unconditionally: ```bash echo -e "\n${GREEN}✅ Skill passed basic security checks${NC}" echo "This skill can be used and shared safely" ``` The messages above are translated into English for reporting; the control flow and executable statements are unchanged. ### Technical Analysis The `safe` variable is only used to conditionally print “No dangerous commands found.” It is not used to: - Set the process exit status. - Suppress the final success verdict. - Count failures. - Stop publication or deployment. - Mark the overall test as failed. Other failed checks in the script likewise only print messages. The concluding success statement is reached regardless of detected findings. This creates a false-negative condition in which the output declares the skill safe even after the same execution reports dangerous content. ### Attack Path 1. A dangerous command or another failing condition is added to the project. 2. `scripts/test_security.sh` is run by a maintainer or release workflow. 3. The relevant check prints an error and may set `safe=false`. 4. The script continues because the failure state is not propagated. 5. The ...[truncated 756 chars]
Remediation
View remediation
&2 exit 1 fi ``` 3. Ensure every failed permission, content, validation, or security-feature test updates the overall failure state. 4. Remove claims such as “can be used and shared safely” unless all mandatory checks completed successfully. 5. Replace fragile regular-expression scanning with static-analysis tools such as ShellCheck and purpose-built behavioral tests. 6. Configure CI to fail when the test script returns a nonzero status. 7. Add a regression test that deliberately inserts or fixtures a known-dangerous pattern and verifies that the script exits nonzero and does not print a success verdict. ]]>
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
Findings (33)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
92% confidence
Finding

The document includes an example showing a '--no-check' mode for cloning unknown repositories, even though it labels the action as high risk and not recommended. In the context of a skill about obtaining and analyzing code from GitHub, documenting a bypass for safety checks can normalize unsafe usage and may lead users or downstream automation to skip validation before interacting with potentially malicious repositories.

Content

Scanner excerpt · SECURITY_IMPROVEMENTS.md (reported line 166)May include surrounding context.

./safe_clone.sh --depth 1 https://github.com/tensorflow/tensorflow

高风险操作:分析未知来源的仓库(不推荐)

./safe_clone.sh --no-check https://github.com/unknown/repo

text

## 🚨 应急响应

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
90% confidence
Finding

The documented --no-check option explicitly allows disabling safety checks in a skill whose core purpose is secure cloning and analysis. Even though it is marked 'not recommended,' exposing a bypass path makes it easier for users or downstream agents to skip validation and clone untrusted repositories without the advertised protections.

Content

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

./scripts/safe_clone.sh --test-url https://github.com/psf/requests

Test with safety checks disabled (not recommended)

./scripts/safe_clone.sh --no-check https://github.com/psf/requests

text

## 🚀 Quick Start

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
85% confidence
Finding

The exposed '--no-check' option allows callers to bypass the script's only pre-clone repository validation step while the tool is presented as 'safe'. In this context, the danger is trust erosion: users may rely on safety guarantees that can be silently disabled, making risky clones more likely.

Content

Scanner excerpt · scripts/safe_clone.sh (reported line 44)May include surrounding context.

sh
echo "  -s, --safe         启用安全检查(默认)"
    echo "  -d, --depth NUM    设置克隆深度(默认: 1)"
    echo "  -t, --temp         使用临时目录"
    echo "  --no-check         禁用安全检查"
    echo ""
    echo "示例:"
    echo "  $0 https://github.com/psf/requests"

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
86% confidence
Finding

This branch implements the '--no-check' behavior by setting 'safe_mode=false', disabling repository inspection before cloning. In a tool marketed as safe, such a bypass undermines the safety model and makes operator mistakes or social-engineering-driven use of unsafe mode more dangerous.

Content

Scanner excerpt · scripts/safe_clone.sh (reported line 312)May include surrounding context.

sh
safe_mode=true
                shift
                ;;
            --no-check)
                safe_mode=false
                shift
                ;;

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
93% confidence
Finding

The script automatically runs chmod +x scripts/safe_clone.sh during a 'test' workflow, modifying file permissions without explicit user consent. In CI, shared workspaces, or code-review contexts, this can tamper with repository state and potentially make another script directly executable, increasing the chance it is run later under mistaken trust.

Content

Scanner excerpt · scripts/test_security.sh (reported line 23)May include surrounding context.

sh
echo "✅ safe_clone.sh 可执行权限正确"
else
    echo "❌ safe_clone.sh 缺少可执行权限"
    chmod +x scripts/safe_clone.sh
    echo "  已修复权限"
fi

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
100% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · scripts/test_security.sh (reported line 32)May include surrounding context.

sh
# 检查是否包含危险命令
dangerous_patterns=(
    "rm -rf /"
    "chmod 777"
    "wget.*-O.*sh"
    "curl.*|.*sh"

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
95% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · scripts/test_security.sh (reported line 32)May include surrounding context.

sh
# 检查是否包含危险命令
dangerous_patterns=(
    "rm -rf /"
    "chmod 777"
    "wget.*-O.*sh"
    "curl.*|.*sh"

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
85% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · README.md (reported line 13)May include surrounding context.

md
2. **Repository Safety Checks** - Size, stars, last update verification via GitHub API
3. **Safe Cloning** - Uses shallow cloning (`--depth 1`) to minimize risk
4. **Dependency Analysis** - Identifies and analyzes dependency files safely
5. **Security Recommendations** - Provides safe installation commands (never auto-executes)
6. **Transparent Reporting** - Detailed operation logs and security assessments

## 🚀 Quick Start

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
85% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · README.md (reported line 43)May include surrounding context.

md
2. **Repository Safety Checks** - Size, stars, last update verification via GitHub API
3. **Safe Cloning** - Uses shallow cloning (`--depth 1`) to minimize risk
4. **Dependency Analysis** - Identifies and analyzes dependency files safely
5. **Security Recommendations** - Provides safe installation commands (never auto-executes)
6. **Transparent Reporting** - Detailed operation logs and security assessments

## 🚀 Quick Start

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
85% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · README.md (reported line 138)May include surrounding context.

md
2. **Repository Safety Checks** - Size, stars, last update verification via GitHub API
3. **Safe Cloning** - Uses shallow cloning (`--depth 1`) to minimize risk
4. **Dependency Analysis** - Identifies and analyzes dependency files safely
5. **Security Recommendations** - Provides safe installation commands (never auto-executes)
6. **Transparent Reporting** - Detailed operation logs and security assessments

## 🚀 Quick Start

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
85% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

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

md
2. **Repository Safety Checks** - Size, stars, last update verification via GitHub API
3. **Safe Cloning** - Uses shallow cloning (`--depth 1`) to minimize risk
4. **Dependency Analysis** - Identifies and analyzes dependency files safely
5. **Security Recommendations** - Provides safe installation commands (never auto-executes)
6. **Transparent Reporting** - Detailed operation logs and security assessments

## 🚀 Quick Start

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
85% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

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

md
2. **Repository Safety Checks** - Size, stars, last update verification via GitHub API
3. **Safe Cloning** - Uses shallow cloning (`--depth 1`) to minimize risk
4. **Dependency Analysis** - Identifies and analyzes dependency files safely
5. **Security Recommendations** - Provides safe installation commands (never auto-executes)
6. **Transparent Reporting** - Detailed operation logs and security assessments

## 🚀 Quick Start

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
85% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

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

md
2. **Repository Safety Checks** - Size, stars, last update verification via GitHub API
3. **Safe Cloning** - Uses shallow cloning (`--depth 1`) to minimize risk
4. **Dependency Analysis** - Identifies and analyzes dependency files safely
5. **Security Recommendations** - Provides safe installation commands (never auto-executes)
6. **Transparent Reporting** - Detailed operation logs and security assessments

## 🚀 Quick Start

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · README.md (reported line 180)May include surrounding context.

Installation

bash
# Ubuntu/Debian
sudo apt install git curl jq

# macOS
brew install git curl jq

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This markdown file uses Chinese throughout, including headings, instructions, and warnings, but does not indicate that the skill supports multiple languages or that Chinese is a required locale. Under the policy rule, forcing a specific language without user opt-in is a natural-language policy violation.

Content

No source excerpt is available for this finding.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · SECURITY_IMPROVEMENTS.md (reported line 97)May include surrounding context.

md
### 1. 最小权限原则
- 只请求必要的二进制文件(git, ls, cat)
- 不请求 root 或 sudo 权限
- 限制文件系统访问范围

### 2. 防御性编程

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill claims it never auto-executes package installation, yet elsewhere provides directly runnable installation commands such as pip install --user -r requirements.txt and npm ci --ignore-scripts. In a security-focused skill, this inconsistency can mislead users or downstream agents into overtrusting the guidance and executing dependency installation from untrusted repositories without sufficient review.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill recommends a third-party Python package mirror without discussing trust, integrity, privacy, or organizational policy implications. Users may unknowingly fetch packages and leak dependency metadata through an unvetted mirror, undermining the skill's stated security-first posture.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

Prescribing a specific locale-specific package mirror without user opt-in or justification steers users toward an alternate software supply path that may not match their threat model or compliance requirements. This is especially risky in a security-oriented skill because it normalizes changing package provenance without adequate explanation.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The OWASP compliance section asserts controls like authentication, session management, access control, and cryptographic practices, but the described implementation does not include mechanisms supporting those claims. This creates a false sense of assurance around security properties the skill does not actually provide, which can cause unsafe reliance in higher-risk environments.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The script’s user-facing description and help/log messages are written in Chinese, and there is no indication that the tool is intentionally region-specific or that users can select another language. This creates a natural-language policy issue because the skill effectively forces a specific language without opt-in.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

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

md
log_info "检查仓库信息: $owner_repo"
    
    # 使用 GitHub API 获取仓库信息
    local api_url="https://api.github.com/repos/$owner_repo"
    local response
    
    if command -v curl &> /dev/null; then

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · scripts/safe_clone.sh (reported line 82)May include surrounding context.

sh
log_info "检查仓库信息: $owner_repo"
    
    # 使用 GitHub API 获取仓库信息
    local api_url="https://api.github.com/repos/$owner_repo"
    local response
    
    if command -v curl &> /dev/null; then

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The script advertises itself as a 'safe' cloning tool but will recursively delete any existing target directory after a single interactive confirmation. If a user supplies or accepts an unsafe path, this can destroy arbitrary local data and the 'safe' branding increases the risk of over-trust.

Content

No source excerpt is available for this finding.

Unsafe Defaults

Medium
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.

Content

Scanner excerpt · scripts/safe_clone.sh (reported line 313)May include surrounding context.

sh
shift
                ;;
            --no-check)
                safe_mode=false
                shift
                ;;
            -d|--depth)