T09 · Insecure Skill Coding Practices
- Location
SKILL.md:53- Finding
GitHub Token Exposure Through Authenticated Clone URL
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill performs a coherent repository setup workflow, but it under-protects GitHub tokens and can run untrusted project install/build logic with the user's normal environment.
Review before installing. Use GitHub CLI, SSH, or a credential helper instead of token-in-URL cloning, do not store GH_TOKEN in a shell profile, and only run dependency or build commands for repositories you trust or inside an isolated environment without unrelated secrets.
SKILL.md:53GitHub Token Exposure Through Authenticated Clone URL
SKILL.md:43Shell Command Injection Through Unvalidated Template Parameters
SKILL.md:99Automatic Execution of Untrusted Repository Dependency and Build Logic
The skill instructs cloning with https://${GH_TOKEN}@github.com/..., which embeds the GitHub token directly in the command line and remote URL. This can expose the credential through shell history, process inspection, logs, terminal recordings, or persisted Git remote configuration, making accidental token disclosure significantly more likely.