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/apexiq/skillsmith/git_expertnpx skills add ApexIQ/skillsmith --skill git_expertgit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/git_expert)<a href="https://agentmods.dev/skills/apexiq/skillsmith/git_expert"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/git_expert.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 | $0.00031 | $0.00819 |
| Opus 5 | $0.00015 | $0.00409 |
| Sonnet 5 | $0.00006 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
git-expert 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🌿 Git Expert — Production-Grade Source Control
Philosophy: Git history is a technical document, not a personal diary. Every commit should be a discrete, atomic improvement with a clear record of "why" and "what."
1. When to Use This Skill
- Creating new branches or managing worktrees
- Writing commit messages (Conventional Commits)
- Preparing Pull Requests or structured diffs
- Navigating complex git history (rebase, squash, cherry-pick)
- Resolving merge conflicts
- Organizing parallel development streams
2. Conventional Commits (Automation-Ready)
Always use the Conventional Commits specification for automated changelogs and versioning.
Structure
<type>[optional scope]: <description>
Types
feat: A new featurefix: A bug fixdocs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, etc)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary tools and libraries
Example
feat(auth): add OIDC provider support for team-service
fix(ui): resolve clipping issue on mobile headers
docs: update competitive audit findings in README
3. Worktree Management (Context Switching)
Use git worktree to work on multiple branches simultaneously without affecting your main working directory. This is critical for high-velocity teams.
Workflow
- Create:
git worktree add ../feature-branch feature-branch - List:
git worktree list - Remove:
git worktree remove ../feature-branch
Rule: Always keep worktrees outside the main project folder to avoid nested repository confusion.
4. Branching Strategy
| Branch | Purpose |
|---|---|
main |
Production-ready, stable code. |
develop |
Integration branch for features. |
feat/* |
Feature-specific development. |
fix/* |
Bug fixes for existing features. |
hotfix/* |
Critical production fixes. |
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 · 92 lines · 31 tokens per session scan A f6d365686eef
git-expert is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 819 once invoked, about $0.0002 per session on Opus 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
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
shep-kit:commit-pr
Use when ready to commit, push, and create a PR with CI verification. Triggers include "commit and pr", "push pr", "create pr", "ship it", or when implementation is complete and needs CI validation. Watches CI and auto-fixes failures. Part of the Shep autonomous SDLC platform — https://shep.bot.
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…