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 agentmods add skills/openminis/minisskills/github-sync-helpernpx skills add OpenMinis/MinisSkills --skill github-sync-helpergit clone --depth 1 https://github.com/OpenMinis/MinisSkillsWhat 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 | $0.00124 | $0.02941 |
| Opus 5 | $0.00062 | $0.01470 |
| Sonnet 5 | $0.00025 | $0.00588 |
| Haiku 4.5 | $0.00012 | $0.00294 |
Grade A, and why
github-sync-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 2d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objectives
Codify GitHub/Git "basic operations" and common collaboration workflows into:
- A clear command quick reference (explanation + when to use)
- Executable one-click scripts (to avoid repetitive manual steps)
- Common outputs that are "numbered" whenever possible, so the user can reply with a number to choose an item directly, such as from a repository list
Security and Constraints (Must Be Followed)
| No. | Rule | Reason |
|---|---|---|
| 1 | Do not output tokens: No command may echo or print $GITHUB_TOKEN to stdout |
Prevent leaks |
| 2 | Require a second confirmation for dangerous operations: deleting branches, emptying directories, forced overwrites, force pushes, and direct pushes to main | These operations are hard to reverse |
| 3 | Use "branch + PR" collaboration by default; only "push directly to main" when the user explicitly requests it | Reduce the risk of damaging the main branch |
| 4 | Run git status before push/pull |
Prevent accidental commits or overwrites |
How to Run
- Script entry point:
sh /var/minis/skills/github-sync-helper/scripts/gh_sync.sh <command> [options]
The script runs in the "current Git repository directory" and must be run inside a repository.
Quick Reference for Basic Git/GitHub Operations (Explanation + Corresponding Script)
| No. | Category | Operation | One-sentence explanation | Common command | Script support |
|---|---|---|---|---|---|
| 1 | Initialize | init | Turn the current directory into a Git repository | git init |
init |
| 2 | Get code | clone | Download a repository from a remote to local | git clone <url> |
clone |
| 3 | Remote | remote | Manage remotes such as origin/upstream | git remote -v/add/set-url/remove |
remotes/add-remote/add-upstream/set-remote-url/remove-remote |
| 4 | Branch | branch | View, create, or delete branches | git branch -a/-d/-D |
branches/create-branch/delete-branches |
| 5 | Switch | checkout/switch | Switch to a branch | git switch <b> |
checkout |
| 6 | View changes | status/diff/log | View working tree changes, diffs, or history | git status git diff git log |
status/diff/log |
| 7 | Stage | add | Add changes to the staging area | git add -A |
add |
| 8 | Commit | commit | Package the staging area into a commit | git commit -m "..." |
commit |
| 9 | Sync | fetch/pull/push | Fetch, merge, or push commits | git fetch git pull git push |
fetch/pull/push/push-main |
| 10 | Merge | merge/rebase | Merge branch history | git merge git rebase |
merge/rebase (use with caution) |
| 11 | Stash | stash | Temporarily set aside uncommitted changes | git stash |
stash |
| 12 | Tag | tag | Add a version tag to a commit | git tag |
tag |
| 13 | Submodule | submodule | Manage subrepository dependencies | git submodule |
submodule |
| 15 | GitHub platform | issues/labels/milestones/releases/actions | Manage platform objects through the GitHub API | (API) | gh-issues-list and others (see below) |
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.
- 2d ago First seen · 177 lines · 124 tokens per session scan A 775794c9d403
github-sync-helper is a skill published in the GitHub repository OpenMinis/MinisSkills (394 stars, last pushed 13d ago), licensed MIT. It adds 124 tokens to every session and 2,941 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.