← Back to Skills Marketplace
GitHub Token
by
Danny Shmueli
· GitHub ↗
· v1.0.0
1699
Downloads
1
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install github-token
Description
Interact with GitHub using Personal Access Tokens. Secure, user-controlled access - no OAuth, no full account access. Clone, push, branch, PR, issues. Use when user wants to work with GitHub repos.
README (SKILL.md)
GitHub PAT
Interact with GitHub using Personal Access Tokens. User controls access via PAT scopes.
Setup
User provides their PAT:
1. Create PAT at github.com/settings/tokens
2. Select scopes (repo for full, public_repo for public only)
3. Provide token to agent
Store in TOOLS.md or pass via --token.
Commands
# List repos you have access to
python3 scripts/gh.py repos [--token TOKEN]
# Clone a repo
python3 scripts/gh.py clone owner/repo [--token TOKEN]
# Create branch
python3 scripts/gh.py branch \x3Cbranch-name> [--repo owner/repo]
# Commit and push
python3 scripts/gh.py push "\x3Cmessage>" [--branch branch] [--repo owner/repo]
# Open a pull request
python3 scripts/gh.py pr "\x3Ctitle>" [--body "description"] [--base main] [--head branch]
# Create an issue
python3 scripts/gh.py issue "\x3Ctitle>" [--body "description"] [--repo owner/repo]
# View repo info
python3 scripts/gh.py info owner/repo
Security Model
- User controls access via PAT scopes
- No OAuth - no "allow full access" prompts
- Least privilege - user creates PAT with minimal needed scopes
- Fine-grained PATs supported for specific repo access
Token Storage
Agent stores token in TOOLS.md under ### GitHub section. Never expose in logs or messages.
Usage Guidance
This skill appears to implement the described GitHub PAT operations, but take these precautions before installing or using it: (1) do not paste your PAT into chat; prefer setting GITHUB_TOKEN in a secure environment (not a shared TOOLS.md). (2) Avoid passing PAT via --token on the command line (it can appear in process lists). (3) Review and consider modifying scripts/gh.py to avoid embedding tokens into HTTPS remote URLs — embedding the token can cause it to be written into .git/config and persist on disk. Use a git credential helper or the GitHub CLI (gh) or OAuth device flow instead if possible. (4) Update the skill metadata to declare that 'git' is required; lack of that declaration is an incoherence. (5) Inspect .git/config and your working directories after use to ensure no credentials were saved. If you don't accept these risks, do not install or run the skill; if you proceed, review and harden the token-handling code (e.g., use HTTP Authorization header for API calls only, use git credential helpers, avoid storing tokens in plain text).
Capability Analysis
Type: OpenClaw Skill
Name: github-token
Version: 1.0.0
The OpenClaw skill 'github-token' is designed to interact with GitHub using Personal Access Tokens (PATs). The `SKILL.md` clearly outlines its purpose and commands, and includes an instruction for the agent to store the token securely in `TOOLS.md` and 'Never expose in logs or messages'. The `scripts/gh.py` implements standard GitHub API calls and Git CLI commands (`git clone`, `git push`, etc.) using the provided PAT. While PATs are sensitive and are injected into Git URLs for authentication in `cmd_clone` and `cmd_push`, this is a common and expected method for authenticating Git operations with PATs and is not indicative of malicious intent. There is no evidence of data exfiltration to unauthorized endpoints, malicious execution beyond the stated purpose, persistence mechanisms, or prompt injection attempts against the agent. The skill's behavior is aligned with its stated purpose.
Capability Assessment
Purpose & Capability
The name/description match the included code: the Python CLI uses a GitHub PAT to call the API and run git operations (clone, push, PRs, issues). However the registry metadata claims no required binaries while the script relies heavily on the git binary via subprocess calls — that is an inconsistency (the skill should declare 'git' as a required binary). Other than that, requested capabilities align with the stated purpose.
Instruction Scope
SKILL.md tells the agent to accept a PAT and to 'Store in TOOLS.md or pass via --token'. Storing tokens in a plain text TOOLS.md or passing tokens on the command line are insecure practices. The included script embeds PATs into HTTPS URLs for clone/push which can cause tokens to be written into .git/config or otherwise persist on disk. The instructions ask the agent to handle tokens but give unsafe storage guidance and do not warn about process-list exposure when using --token on the CLI. The SKILL.md's 'Never expose in logs' guidance is good but insufficient; the code's use of subprocess and URL injection can still lead to accidental exposure.
Install Mechanism
This is instruction-only with one script file; there is no install spec or remote downloads. That minimizes supply-chain risk — nothing is fetched from arbitrary URLs at install time.
Credentials
The skill declares no required env vars, and the code reads GITHUB_TOKEN from the environment (DEFAULT_TOKEN). That is reasonable. However SKILL.md's explicit instruction to save the token in TOOLS.md is disproportionate and insecure. Also the runtime behavior (embedding the token into HTTPS URLs or accepting it as a CLI arg) increases chances of exposure (saved in .git/config or visible in process lists). There are no unrelated credentials requested, so the scope of credentials is narrow, but the handling choices are risky.
Persistence & Privilege
always is false and the skill doesn't request persistent platform privileges. It does, however, encourage storing the token in a file the agent controls (TOOLS.md), which would be persistence of a secret under the agent's files — the skill itself does not change other skills or system-wide settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install github-token - After installation, invoke the skill by name or use
/github-token - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Secure GitHub via PAT
Metadata
Frequently Asked Questions
What is GitHub Token?
Interact with GitHub using Personal Access Tokens. Secure, user-controlled access - no OAuth, no full account access. Clone, push, branch, PR, issues. Use when user wants to work with GitHub repos. It is an AI Agent Skill for Claude Code / OpenClaw, with 1699 downloads so far.
How do I install GitHub Token?
Run "/install github-token" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is GitHub Token free?
Yes, GitHub Token is completely free (open-source). You can download, install and use it at no cost.
Which platforms does GitHub Token support?
GitHub Token is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created GitHub Token?
It is built and maintained by Danny Shmueli (@dannyshmueli); the current version is v1.0.0.
More Skills