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 asgarovf/locusai --skill git-essentialsgit clone --depth 1 https://github.com/asgarovf/locusaiWrote 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/asgarovf/locusai/git-essentials)<a href="https://agentmods.dev/skills/asgarovf/locusai/git-essentials"><img src="https://agentmods.dev/badge/skills/asgarovf/locusai/git-essentials/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/asgarovf/locusai/git-essentials"><img src="https://agentmods.dev/badge/skills/asgarovf/locusai/git-essentials.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.00034 | $0.00681 |
| Opus 5.5 | $0.00014 | $0.00272 |
| Sonnet 5.5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
git-essentials 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Essentials
When to use this skill
- Creating and managing branches
- Resolving merge conflicts
- Rebasing and cleaning up history
- Cherry-picking commits
- Investigating history with git log/blame/bisect
- Recovering from mistakes (reset, revert, reflog)
Branching Strategy
Branch naming
feat/<issue>-<short-description>
fix/<issue>-<short-description>
chore/<short-description>
release/<version>
hotfix/<issue>-<description>
Common workflows
# Create feature branch from main
git checkout main && git pull
git checkout -b feat/123-add-auth
# Keep branch up to date with main
git fetch origin
git rebase origin/main
# Squash commits before merge
git rebase -i origin/main
# Mark commits as 'squash' or 'fixup'
Conflict Resolution
Strategy
- Understand both sides of the conflict
- Determine which changes to keep (or merge both)
- Test after resolution
- Never blindly accept "ours" or "theirs"
# See which files conflict
git status
# Use merge tool
git mergetool
# After resolving manually
git add <resolved-files>
git rebase --continue # or git merge --continue
History Investigation
# Search commits by message
git log --grep="fix auth"
# Find who changed a line
git blame <file> -L <start>,<end>
# Find which commit introduced a bug
git bisect start
git bisect bad HEAD
git bisect good v1.0.0
# Git will binary search — test each commit and mark good/bad
# Show changes to a specific function
git log -p -S "functionName" -- <file>
Recovery
# Undo last commit (keep changes staged)
git reset --soft HEAD~1
# Find lost commits
git reflog
# Restore a deleted branch
git checkout -b <branch> <reflog-sha>
# Revert a pushed commit (creates new commit)
git revert <sha>
# Unstage files
git restore --staged <file>
# Discard working tree changes
git restore <file>
Best Practices
- Commit often — small, atomic commits are easier to review and revert
- Pull before push — avoid unnecessary merge commits
- Don't rewrite shared history — never force-push to main/master
- Use
.gitignore— keep build artifacts, secrets, and IDE files out - Write meaningful messages — future-you will thank present-you
- Review diffs before committing —
git diff --stagedcatches mistakes
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 · 115 lines · 34 tokens per session scan A 67c4d10a0710
git-essentials is a skill published in the GitHub repository asgarovf/locusai (23 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 681 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
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
git-docs
Git 2.49 — repositories, branching, merging, rebasing, remotes, submodules, hooks, internals, workflows.
git-workflow
Essential Git patterns for effective version control, eliminating redundant Git guidance per agent.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
git-expert
Expert-level Git version control with advanced workflows, branching strategies, and best practices for team collaboration. Use when the user mentions version control, collaboration, or workflow, or when the task involves Essential Git Commands, Advanced Git Techniques, Branching Strategies, or Conflict Resolution.