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 arnabdeypolimi/claude_code_setup --skill git-operationsgit clone --depth 1 https://github.com/arnabdeypolimi/claude_code_setupWrote 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/arnabdeypolimi/claude_code_setup/git-operations)<a href="https://agentmods.dev/skills/arnabdeypolimi/claude_code_setup/git-operations"><img src="https://agentmods.dev/badge/skills/arnabdeypolimi/claude_code_setup/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/arnabdeypolimi/claude_code_setup/git-operations"><img src="https://agentmods.dev/badge/skills/arnabdeypolimi/claude_code_setup/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.00052 | $0.01055 |
| Opus 5.5 | $0.00021 | $0.00422 |
| Sonnet 5.5 | $0.00010 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
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 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Operations
Reusable patterns for common git operations in this repository.
Branch Operations
Create Feature Branch
git checkout main
git pull origin main
git checkout -b feature/<name>
Create Task Branch (Cascade)
git checkout <parent-branch>
git checkout -b task-N-<description>
Delete Branch
git branch -d <branch-name> # Safe delete
git branch -D <branch-name> # Force delete
git push origin --delete <branch-name> # Delete remote
List Branches
git branch # Local branches
git branch -r # Remote branches
git branch -a # All branches
Commit Operations
Standard Commit
git add <files>
git commit -m "<type>(<scope>): <description>"
Commit Types
feat- New featurefix- Bug fixdocs- Documentationstyle- Formattingrefactor- Code restructuringtest- Testschore- Maintenance
Amend Last Commit
git commit --amend -m "new message" # Change message only
git add <files> && git commit --amend --no-edit # Add files to last commit
View Commit History
git log --oneline -10 # Recent commits
git log --oneline --graph -20 # With graph
git log --oneline -- <file> # For specific file
Staging Operations
Stage Files
git add file1.py file2.py # Specific files
git add "*.py" # By pattern
git add . # All changes
Unstage Files
git restore --staged <file>
View Changes
git diff # Unstaged changes
git diff --staged # Staged changes
Sync Operations
Fetch Updates
git fetch origin
Pull Changes
git pull origin <branch>
Push Changes
git push origin <branch> # Normal push
git push -u origin <branch> # Set upstream
git push --force-with-lease origin <branch> # Force push (use carefully!)
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 · 224 lines · 52 tokens per session scan A b6dbd18a321d
git-operations is a skill published in the GitHub repository arnabdeypolimi/claude_code_setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,055 once invoked, about $0.0002 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
quality-gates
Graduated pre-commit quality checks that scale with project complexity and user tier. Level 0 for Builder-tier small projects, up to Level 4 for enterprise codebases. Thresholds configurable in architecture.md.
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
git
Source-control safety for Git. Two rules apply whether or not you read the body. First, never commit, amend, push, tag, rebase, cherry-pick, revert, or reset --hard unless the user asked for that exact write in this session. An explicit request to create a new commit counts anywhere in the user's own task text, but it…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.