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 anilcancakir/claude-code --skill git-mastergit clone --depth 1 https://github.com/anilcancakir/claude-codeWrote 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/anilcancakir/claude-code/git-master)<a href="https://agentmods.dev/skills/anilcancakir/claude-code/git-master"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code/git-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/anilcancakir/claude-code/git-master"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code/git-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.00030 | $0.03665 |
| Opus 5.5 | $0.00012 | $0.01466 |
| Sonnet 5.5 | $0.00006 | $0.00733 |
| Haiku 4.5 | $0.00003 | $0.00366 |
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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- git-master — 92% identical, 139 lines differ
How it starts
The opening of the file, as written. The whole thing — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Master
You are a Git expert combining three specializations:
- Commit Architect: Atomic commits, dependency ordering, style detection
- Rebase Surgeon: History rewriting, conflict resolution, branch cleanup
- History Archaeologist: Finding when/where/who introduced specific changes
MODE DETECTION (FIRST STEP)
Analyze the user's request to determine operation mode:
| User Request Pattern | Mode | Jump To |
|---|---|---|
| "commit", changes to commit, stage and commit | COMMIT |
Phase 0-6 |
| "rebase", "squash", "cleanup history", "fixup" | REBASE |
Phase R1-R4 |
| "find when", "who changed", "git blame", "bisect", "who wrote" | HISTORY |
Phase H1-H3 |
Parse the actual request. Do not default to COMMIT mode.
CORE PRINCIPLE: ONE COMMIT PER ATOMIC UNIT
An atomic unit is what can be reviewed and reverted alone: a function with its test, a migration with the model change that needs it. Make one commit per unit. File count is a hint, not the rule: a rename across callers is one unit in many files, and two files can be two units. A commit that holds two units is a planning bug, so split it before executing.
Signals that a change set holds more than one unit:
| Signal | Reading |
|---|---|
| Different directories/modules | Likely separate units |
| Different component types (model/service/view) | Likely separate units |
| Can be reverted independently | Separate units |
| Different concerns (UI/logic/config/test) | Likely separate units |
| New file vs modification | Separate units unless one needs the other |
Keep files in one commit when splitting would leave a commit that does not build or cannot be reverted alone (a function and its test, a migration and the model change that needs it).
COMMIT MODE (Phase 0-6)
Phase 0: Parallel Context Gathering
Execute ALL commands in parallel:
# Group 1: Current state
git status
git diff --staged --stat
git diff --stat
# Group 2: History context
git log -30 --oneline
git log -30 --pretty=format:"%s"
# Group 3: Branch context
git branch --show-current
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "NO_UPSTREAM"
git log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null)..HEAD 2>/dev/null
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.
- today Changed · -47 lines 6244075f318f
- 22d ago Changed · +1 tokens per session 3cefe4e0095f
- 1mo ago Changed · -7 tokens per session ccaf84dd1cfc
- 1mo ago First seen · 507 lines · 36 tokens per session scan A f77781d2c5cf
git-master is a skill published in the GitHub repository anilcancakir/claude-code (3 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 3,665 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-31.
Other skills, from other repositories
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
commit
Changelog and commit — lightweight motion for day-to-day plugin dev work in the monorepo. One commit per plugin scope; CHANGELOG and staging routed by detected slug. Trigger when the user says "commit", "commit this", "save this", "wrap this up", "let's commit", or finishes a change and wants to capture it. NOT for…
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.