mastering-git-cli

Pass

Audited by Gen Agent Trust Hub on Sep 1, 2026

Risk Level: SAFEINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTIONDYNAMIC_EXECUTIONREMOTE_CODE_EXECUTIONEXTERNAL_DOWNLOADSDATA_EXFILTRATION
Full Analysis
  • [INDIRECT_PROMPT_INJECTION]: The skill ingests untrusted data from local Git repositories through commands like git log, git status, and git branch, as well as scripts like submodule-report.sh which reads .gitmodules. This metadata can be influenced by external contributors, creating a surface for indirect prompt injection. The skill lacks explicit boundary markers or sanitization for this interpolated data.
  • Ingestion points: scripts/git-health-check.sh, scripts/submodule-report.sh, and various documentation commands (specify logs, status, branch lists).
  • Boundary markers: Absent.
  • Capability inventory: Includes git commit, git push, git merge, and git worktree operations which could be manipulated by injected instructions.
  • Sanitization: None detected on git output processing.
  • [COMMAND_EXECUTION]: The skill provides several shell scripts (setup-agent-worktrees.sh, cleanup-agent-worktrees.sh, git-health-check.sh, submodule-report.sh) that perform repository management, filesystem checks, and status reporting using standard Unix utilities (sed, grep, awk, find, du).
  • [DYNAMIC_EXECUTION]: The skill instructs the user and agent to generate shell scripts dynamically for use with git bisect run (e.g., test.sh). This script generation and subsequent execution is a standard Git workflow but involves creating executable content at runtime.
  • [REMOTE_CODE_EXECUTION]: The documentation recommends the installation of the pre-commit framework using pip install pre-commit. This downloads and installs code from the Python Package Index (PyPI). This is considered safe as it targets a well-known official registry for a legitimate development tool.
  • [DATA_EXPOSURE]: The skill's documentation (SKILL.md, references/recovery.md, references/git-2025-features.md) references sensitive local file paths such as ~/.ssh/id_rsa and ~/.ssh/id_ed25519.pub for the purpose of configuring commit signing and SSH authentication. While these are standard Git configuration paths, they point to the user's private cryptographic material.
Audit Metadata
Risk Level
SAFE
Analyzed
Sep 1, 2026, 01:24 AM
Security Audit — agent-trust-hub — mastering-git-cli