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 Miaoge-Ge/coding-agent-skills --skill github-mastergit clone --depth 1 https://github.com/Miaoge-Ge/coding-agent-skillsWrote 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/miaoge-ge/coding-agent-skills/github-master)<a href="https://agentmods.dev/skills/miaoge-ge/coding-agent-skills/github-master"><img src="https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/github-master/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/miaoge-ge/coding-agent-skills/github-master"><img src="https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/github-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00085 | $0.01111 |
| Opus 5.5 | $0.00034 | $0.00444 |
| Sonnet 5.5 | $0.00017 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
github-master 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Master
Commits are cheap, lost work is recoverable (reflog), and history is communication. Rebase your own local work, never shared history; force-push only with
--force-with-lease.
When to Use
- Git commands or trouble: conflicts, detached HEAD, lost commits, undo/redo.
- Repo management, PRs, issues, branch protection, CODEOWNERS.
- Branching strategy or GitHub Actions CI/CD.
- Recovering or rewriting history safely.
When NOT to Use
- Writing application code → relevant language skill.
- High-level system design →
software-architect. - Shell logic inside workflows →
bash-scripting-expert.
Core Principles
1. Core operations & recovery
- Fluent with
add/commit/push/pull/branch/merge/rebase, plusstash,cherry-pick,bisect,worktree. - Almost nothing is truly lost:
git reflogfinds detached/reset-away commits. Prefergit revert(safe, new commit) overreset --hardon anything shared. - Undo map: un-add →
restore --staged; amend last (local) commit →commit --amend; move branch pointer →reset; recover →reflog+checkout -b.
2. Rewriting history — the safety rule
- Rewrite only local, unpushed commits (interactive rebase to clean up). Never rewrite shared/
mainhistory. - If you must update a shared branch after rebase, use
git push --force-with-lease(refuses if someone else pushed) — never plain--force.
3. Workflow & commits
- GitHub Flow (main + short-lived feature branches) for most teams; Git Flow only for heavy release trains. Protect
mainwith required reviews + status checks; use CODEOWNERS and PR/issue templates. - Conventional Commits (
feat:,fix:,docs:) enable automated changelogs/SemVer. Small, focused PRs that explain why; link issues (Fixes #123). Know merge strategies: squash (clean linear history), merge commit (preserve context), rebase (linear, no merge commit).
4. GitHub Actions CI/CD
- Workflows in
.github/workflows/*.yml: triggers (on), jobs, steps, runners. Cache dependencies (actions/cacheorsetup-*cache), use matrix builds, pin action versions, and scopepermissions:to least privilege. Secrets via encrypted Secrets/Variables — never echo them.
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 · 84 lines · 85 tokens per session scan A 14ca548722de
github-master is a skill published in the GitHub repository Miaoge-Ge/coding-agent-skills (7 stars, last pushed 4mo ago), licensed MIT. It adds 85 tokens to every session and 1,111 once invoked, about $0.0003 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-31.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
gitlab-mcp-skill
Use this skill when working with the GitLab MCP server tools for merge requests, issues, repositories, pipelines, work items, variables, dependency proxy, vulnerabilities, webhooks, search, CI catalog, and related GitLab workflows.
turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
releasing-prod
A controlled process for deploying already tested changes to the production environment. Production is the live environment used by users, and this process includes owner approval, database migration checks, deployment, and smoke tests.
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.
npm-trusted-publishing
Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration.