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/nguyenthanhtat/screen1-claude/gitnpx skills add nguyenthanhtat/screen1-claude --skill gitgit clone --depth 1 https://github.com/nguyenthanhtat/screen1-claudeWrote 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/nguyenthanhtat/screen1-claude/git)<a href="https://agentmods.dev/skills/nguyenthanhtat/screen1-claude/git"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/git.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.1 | $0.00000 | $0.02753 |
| Opus 5 | $0.00000 | $0.01376 |
| Sonnet 5 | $0.00000 | $0.00551 |
| Haiku 4.5 | $0.00000 | $0.00275 |
Grade A, and why
git 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 5d 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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Skill Suite
Purpose
Comprehensive Git expertise covering all workflows, from basic commits to advanced operations, conflict resolution, and team collaboration patterns.
Version
- Version: 1.0.0
- Last Updated: 2025-02-11
- Git Version: 2.30+
- Compatibility: All major Git hosting platforms (GitHub, GitLab, Bitbucket)
How to Use This Skill
Direct Sub-Skill Access
Use skill paths to access specific functionality:
/git/basics- Repository setup, commits, and fundamental workflows/git/branching- Branch management, merging, and rebasing/git/history- Commit history, diffs, and code archaeology/git/remote- Remote repository operations and syncing/git/conflicts- Merge and rebase conflict resolution/git/undo- Undo changes and recover lost work/git/workflows- Team workflows (GitHub Flow, Git Flow, etc.)/git/advanced- Stash, cherry-pick, hooks, and power features
Chat Command Examples
# Basic operations
/git/basics help me commit my changes with a good message
# Branching
/git/branching create feature branch and merge to main
# Conflict resolution
/git/conflicts resolve merge conflict in src/app.js
# History inspection
/git/history find when this bug was introduced
# Undo mistakes
/git/undo I accidentally committed to main, help me undo
# Remote operations
/git/remote sync my fork with upstream
# Team workflows
/git/workflows setup GitHub Flow for our team
# Advanced features
/git/advanced use stash to switch contexts quickly
Auto-Routing (Claude Decides)
If you just use /git, Claude will analyze your request and automatically route to the appropriate sub-skill.
Examples:
- "How do I commit my changes?" → routes to
/basics - "Create a new branch" → routes to
/branching - "I have a merge conflict" → routes to
/conflicts - "View commit history" → routes to
/history - "Undo last commit" → routes to
/undo - "Push to GitHub" → routes to
/remote - "What's GitHub Flow?" → routes to
/workflows - "Save work without committing" → routes to
/advanced
What ships with it
13 files 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.
- 5d ago First seen · 426 lines · 0 tokens per session scan A 646de612903b
git is a skill published in the GitHub repository nguyenthanhtat/screen1-claude (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,753 tokens. 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
create-hotfix
Create a hotfix (patch) release branch for an Azure SDK Rust crate.