Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ericwang915/PythonClaw --skill githubgit clone --depth 1 https://github.com/ericwang915/PythonClawWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ericwang915/pythonclaw/github)<a href="https://agentmods.dev/skills/ericwang915/pythonclaw/github"><img src="https://agentmods.dev/badge/skills/ericwang915/pythonclaw/github/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ericwang915/pythonclaw/github"><img src="https://agentmods.dev/badge/skills/ericwang915/pythonclaw/github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.00729 |
| Opus 5.5 | $0.00023 | $0.00292 |
| Sonnet 5.5 | $0.00011 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
github scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub
When to Use
- List repositories, issues, or pull requests
- Create or view issues and PRs
- Check CI/workflow run status
- Create or manage releases
- Query GitHub REST or GraphQL API
- Review PR checks, comments, or status
When NOT to Use
- General git commands (commit, push, branch) — use
gitdirectly - Cloning public repos — use
git clonewithout this skill - Tasks that don't involve GitHub (e.g., local file operations)
Setup
- For gh CLI: Install with
brew install gh(macOS) or see cli.github.com - Auth: Run
gh auth loginor setGH_TOKEN/GITHUB_TOKEN - For Python fallback: Create a PAT at https://github.com/settings/tokens and add to
pythonclaw.json:
"skills": {
"github": {
"token": "ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
Usage/Commands
gh CLI (Preferred)
| Action | Command |
|---|---|
| List PRs | gh pr list --repo owner/repo |
| View PR | gh pr view <number> --repo owner/repo |
| Create PR | gh pr create --repo owner/repo --title "..." --body "..." |
| PR checks | gh pr checks <number> --repo owner/repo |
| List issues | gh issue list --repo owner/repo |
| Create issue | gh issue create --repo owner/repo --title "..." --body "..." |
| Workflow runs | gh run list --repo owner/repo |
| View run | gh run view <run_id> --repo owner/repo |
| REST API | gh api /repos/owner/repo |
| GraphQL | gh api graphql -f query='{ viewer { login } }' |
Python Fallback
When gh is not installed or for custom logic:
python {skill_path}/gh.py <command> [options]
repos <user>— list user's public repositoriesrepo <owner/repo>— get repository detailsissues <owner/repo>— list open issuescreate-issue <owner/repo> --title "..." --body "..."— create an issueprs <owner/repo>— list open pull requestspr <owner/repo> <number>— get PR details
Notes
- Prefer
ghCLI for standard operations; it handles auth, pagination, and output formatting - Use
{skill_path}/gh.pywhen you need Python-specific behavior or gh is unavailable - For CI runs,
gh run listandgh run viewshow Actions workflow status
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 79 lines · 57 tokens per session scan A 4edffed44d4e
github is a skill published in the GitHub repository ericwang915/PythonClaw (45 stars, last pushed 10d ago), licensed MIT. It adds 57 tokens to every session and 729 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-manager
A GitHub repository management tool for reviewing code, tracking bugs, setting up automated build and deployment workflows, and managing project work. GitHub is a service where developers store code and collaborate on changes.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
to-tickets
A workflow for turning a written plan or specification into separate GitHub issues, with each issue covering one independently finishable piece of work.
github
GitHub operations: list/create issues, PRs, check CI, manage repos. Requires GHTOKEN.
calendar-scheduling
A calendar tool for checking events and free time, and for creating scheduled events after confirmation. It can work with CalDAV, Google, or Microsoft calendars when configured.
github-repository
A GitHub repository workflow skill for preparing a workspace, applying file patches, pushing a branch, and creating a pull request. A pull request is a proposed code change submitted for review before it is merged.