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/changoo89/claude-pilot/git-masternpx skills add changoo89/claude-pilot --skill git-mastergit clone --depth 1 https://github.com/changoo89/claude-pilotWrote 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/changoo89/claude-pilot/git-master)<a href="https://agentmods.dev/skills/changoo89/claude-pilot/git-master"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/git-master.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00604 |
| Opus 5 | $0.00018 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
git-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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Git Master (Version Control Workflow)
Purpose: Execute Git operations with best practices - commits, branches, PRs Target: Coder Agent after completing implementation
Quick Start
When to Use This Skill
- Stage and commit changes
- Create feature branches
- Create pull requests
Quick Reference
# Stage and commit (ONLY when user requests)
git status && git diff && git add <files>
git commit -m "feat(scope): description\n\nCo-Authored-By: Claude <[email protected]>"
# Create PR: gh pr create --title "Title" --body "Description"
What This Skill Covers
In Scope
- Git staging and committing (on user request)
- Conventional commit messages
- Co-Authored-By attribution
- Branch creation and PR creation
Out of Scope
- Force pushes to main/master
- Git configuration changes
- Repository initialization
Core Principles
Commit ONLY When Requested
CRITICAL: Never create commits unless user explicitly asks.
User requests commit: /commit, "Create a commit", "Commit these changes", "Make a commit for this work"
NOT requests: "Fix this bug", "Add feature X", /03_close
Conventional Commits
Format: type(scope): description
Types: feat, fix, refactor, chore, docs, style, test
Co-Authored-By Attribution
Always include:
Co-Authored-By: Claude <[email protected]>
Integrated Skills
This skill integrates the following specialized git skills:
- git-operations: Push/pull/merge with retry logic and error handling
- using-git-worktrees: Parallel development in isolated workspaces
Further Reading
Internal: @.claude/skills/git-master/REFERENCE.md - Advanced Git patterns, branch strategies, collaboration | @.claude/skills/git-operations/SKILL.md - Safe push/pull/merge operations | @.claude/skills/using-git-worktrees/SKILL.md - Parallel development with worktrees | @.claude/skills/tdd/SKILL.md - Red-Green-Refactor cycle | @.claude/skills/ralph-loop/SKILL.md - Autonomous completion loop | @.claude/skills/vibe-coding/SKILL.md - Code quality standards
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.
- 4d ago First seen · 82 lines · 36 tokens per session scan A 4b6123e7a5c5
git-master is a skill published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 604 once invoked, about $0.0002 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
provisioning-infrastructure
Cloud-native infrastructure knowledge reference covering Kubernetes, Helm, Kustomize, Operators, CRDs, GitOps (ArgoCD, Flux), and IaC (Terraform, Pulumi, CDK). Use when provisioning infrastructure, managing clusters, or working with GitOps workflows.
github-flow-for-claude-on-web
Complete GitHub workflow for Claude Code on the web. ALL GitHub operations MUST use REST API (never gh CLI). Includes branch naming (claude/-sessionId), push retry logic, PR/issue management via API, and complete workflows. Use for all GitHub interactions in Claude Code web environment.
test-design
Automatically design comprehensive E2E test cases for newly implemented vibing.nvim features. Use immediately after completing feature implementation (Phase 5.4) and before running E2E tests. Generates test scenarios covering Happy paths, Error cases, Edge cases, and Integration points with priority ranking…
vibing-orchestrate
Run several independent tasks in parallel by creating worker vibing.nvim chats, handing each one a self-contained brief, and aggregating their results. Use when the user asks for parallel work ("do these three in parallel", "split this across separate chats", "並行でやって", "この2つを別々のチャットで").
vibing-chat-search
Use when the user wants to find a past vibing.nvim conversation by topic — phrases like "前に〜について聞いたことあったっけ", "did we talk about X before", "find that chat where I asked about Y". Searches every chat file under .vibing/chat/ (both User and Assistant content) for a natural-language query, narrows candidates with grep…
vibing-worktree-finish
Remove a git-worktree-backed isolated work area for vibing.nvim chats via natural language — no separate UI. Use when the user wants to clean one up when done ("clean up this worktree", "I'm done with this branch's worktree", "remove the auth-fix worktree").