Borrowing it
Nothing to install: this file belongs to changoo89/claude-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/changoo89/claude-pilot/main/.claude/skills/git-operations/SKILL.mdgit 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-operations)<a href="https://agentmods.dev/skills/changoo89/claude-pilot/git-operations"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/git-operations/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/changoo89/claude-pilot/git-operations"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/git-operations.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.00023 | $0.01268 |
| Opus 5.5 | $0.00009 | $0.00507 |
| Sonnet 5.5 | $0.00005 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
git-operations 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 2mo 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Git Operations
Purpose: Safe push/pull/merge operations with retry logic and error handling Target: All git operations
Quick Start
When to Use This Skill
- Pushing changes to remote
- Pulling latest changes
- Merging branches
- Resolving merge conflicts
Quick Reference
# Push with retry (3 attempts, 2s delay)
git_push_with_retry() {
local branch="${1:-$(git rev-parse --abbrev-ref HEAD)}"
for attempt in {1..3}; do
git push origin "$branch" 2>&1 && return 0
echo "Retry $attempt/3..." && sleep 2
done
return 1
}
# Pull with fast-forward only
git pull --ff-only || echo "Manual merge required"
Core Operations
Push with Retry
Purpose: Handle transient network failures with exponential backoff (3 attempts, 2s/4s/8s delay)
git_push_with_retry() {
local remote="${1:-origin}"
local branch="${2:-$(git rev-parse --abbrev-ref HEAD)}"
local max_attempts=3
local wait_times=(2 4 8) # Exponential backoff
echo "🔄 Pushing to $remote/$branch..."
for attempt in $(seq 1 $max_attempts); do
# Attempt push
if git push "$remote" "$branch" 2>&1; then
echo "✓ Push successful"
return 0
fi
local exit_code=$?
local error_output="$(git push "$remote" "$branch" 2>&1 || true)"
# Classify error
if echo "$error_output" | grep -qiE "non-fast-forward|rejected|protected"; then
echo "❌ Push rejected (non-fast-forward or protected branch)"
echo " Run: git pull --rebase && git push"
return 1
elif echo "$error_output" | grep -qiE "authentication|permission|credentials"; then
echo "❌ Authentication error"
echo " Check git credentials: git config --list | grep credential"
return 1
fi
# Retry for network/transient errors
if [ $attempt -lt $max_attempts ]; then
local wait_time=${wait_times[$((attempt-1))]}
echo "⚠️ Push failed (attempt $attempt/$max_attempts), retrying in ${wait_time}s..."
sleep "$wait_time"
else
echo "❌ Push failed after $max_attempts attempts"
return 1
fi
done
return 1
}
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.
- 2mo ago First seen · 185 lines · 23 tokens per session scan A 8bbada5527ab
git-operations is a skill published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 8mo ago), licensed MIT. It adds 23 tokens to every session and 1,268 once invoked, about $0.0001 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
release
Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an…
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
execute-phase
Step executor for units whose triage (unit-lane) decided which steps the unit needs. Implements one triaged step (or all remaining steps), with frozen acceptance, step-local gates, commits, red-gate repair, and diff-size guard. BREAKING: replaced PLAN.md/TASKS.md/progress.md/ACCEPTANCE.md with the unit doc's Tasks…