github-helper

github-helper is a skill for Claude Code, Codex from zrtch/awesome-skills. It costs 60 tokens per session (697 once invoked), scanned A, original, MIT.

A local helper for finding, downloading, updating, and inspecting GitHub repositories. It also maintains a searchable local index of repositories and their locations.

In plain words
What is it for?
Use it when you need to locate a repository, clone or sync it, inspect issues or pull requests, or update the local repository knowledge base.
Why use it?
It gives repository work a consistent starting point and checks local copies before searching GitHub again.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/zrtch/awesome-skills/github-helper
Any agent
npx skills add zrtch/awesome-skills --skill github-helper
Clone the repo
git clone --depth 1 https://github.com/zrtch/awesome-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for github-helper

README.md
[![agentmods](https://agentmods.dev/badge/skills/zrtch/awesome-skills/github-helper.svg)](https://agentmods.dev/skills/zrtch/awesome-skills/github-helper)
Your own site
<a href="https://agentmods.dev/skills/zrtch/awesome-skills/github-helper"><img src="https://agentmods.dev/badge/skills/zrtch/awesome-skills/github-helper.svg" alt="Measured on agentmods" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 697 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00060 $0.00697
Opus 5 $0.00030 $0.00349
Sonnet 5 $0.00012 $0.00139
Haiku 4.5 $0.00006 $0.00070

Measured 3d ago against content hash 96361aaa87f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-helper 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 3d 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.

skills/github-helper/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Helper

Overview

管理本地 GitHub 仓库目录,维护可检索知识库,并为仓库检索、克隆、Issue/PR 跟踪提供统一流程。

Local Repository Directory

Default path: /Users/liuchen/Documents/github

This path is referenced in the knowledge base file: @/Users/liuchen/Documents/github/CLAUDE.md

Core Workflows

1. Initialize or Update Knowledge Base

When first using this skill or when user requests an update:

  1. Check if the github directory exists.
  2. If not found, ask user for the correct path.
  3. Scan the directory using scripts/scan_repos.py.
  4. Update CLAUDE.md using scripts/update_kb.py.

Example:

# Scan repositories
python3 scripts/scan_repos.py /Users/liuchen/Documents/github

# Update knowledge base (pass repos as JSON)
python3 scripts/update_kb.py /Users/liuchen/Documents/github '[{"name":"repo1","path":"/path","summary":"desc"}]'

2. Search for Repository

When user mentions a repository name:

  1. Check local first: Read @/Users/liuchen/Documents/github/CLAUDE.md.
  2. If found locally: Use local path to analyze and answer.
  3. If not found: Search GitHub using gh or GitHub MCP tools.
  4. Offer to download: Ask user whether to clone.

3. Download Repository

When user requests to download/clone:

  1. Clone to the github directory:
    cd /Users/liuchen/Documents/github
    git clone <repo-url>
    
  2. After successful clone, update knowledge base:
    • Run scripts/scan_repos.py to get repo info.
    • Run scripts/update_kb.py to update CLAUDE.md.

4. GitHub Search Integration

Use gh CLI first, then fall back to GitHub MCP:

Search repositories

gh search repos <query> --limit 10

Search issues

gh issue list --repo <owner/repo> --state all --limit 20

Search PRs

gh pr list --repo <owner/repo> --state all --limit 20

Answering Repository Questions

  1. Check whether repository exists in local knowledge base.
  2. If local, prioritize local code inspection.
  3. If information is insufficient, query GitHub issues/PRs/releases.

Read the full file on GitHub · 97 lines

Files

What ships with it

2 files 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.

Changes

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.

  1. 3d ago First seen · 97 lines · 60 tokens per session scan A 96361aaa87f3

Subscribe to this mod's changes

github-helper is a skill published in the GitHub repository zrtch/awesome-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 697 once invoked, about $0.0003 per session on Opus 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens