GitHub Token

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the PAT leaks, anyone with it may be able to read or modify GitHub repositories according to the token scopes.

Why it was flagged

The helper embeds the user's PAT directly into a Git HTTPS URL and passes it as a command argument; clone URLs can be persisted in git remote configuration and command arguments or errors may expose the token.

Skill content
url = f"https://{token}@github.com/{repo}.git" ... subprocess.run(["git", "clone", url, dest], capture_output=True, text=True)
Recommendation

Do not embed PATs in URLs. Use a Git credential helper, askpass flow, or securely scoped environment secret, redact git errors, and clearly declare the credential and required scopes.

What this means

The token could be reused across later tasks or accidentally exposed if TOOLS.md is shared, copied, indexed, or committed.

Why it was flagged

TOOLS.md is persistent agent-readable context; storing a GitHub PAT there creates long-lived secret exposure without retention, deletion, file-permission, or reuse boundaries.

Skill content
Agent stores token in TOOLS.md under `### GitHub` section. Never expose in logs or messages.
Recommendation

Avoid storing PATs in TOOLS.md. Prefer a secret manager or per-session environment variable, and document how to remove or rotate the token.

What this means

Unintended files, unrelated edits, or secrets in the working tree could be committed and pushed to GitHub.

Why it was flagged

The push command automatically stages every local change, commits, and pushes without showing a status/diff or requiring explicit confirmation for the exact files.

Skill content
subprocess.run(["git", "add", "-A"]) ... subprocess.run(["git", "commit", "-m", message] ... ["git", "push", "-u", auth_url, branch])
Recommendation

Show `git status`/diff first, require explicit user confirmation, and allow users to choose specific paths instead of always running `git add -A`.

What this means

Users have less registry-level information to verify where the helper came from and whether required tools are available.

Why it was flagged

The package includes a Python GitHub helper and documents python3/git command use, but provenance and runtime dependency metadata are incomplete.

Skill content
Source: unknown; Homepage: none; Required binaries (all must exist): none
Recommendation

Declare the project source/homepage and required binaries, especially git and python3, so users can verify provenance and prerequisites.