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/joshuadavidthomas/opencode-agent-skills/git-helpernpx skills add joshuadavidthomas/opencode-agent-skills --skill git-helpergit clone --depth 1 https://github.com/joshuadavidthomas/opencode-agent-skillsWrote 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/joshuadavidthomas/opencode-agent-skills/git-helper)<a href="https://agentmods.dev/skills/joshuadavidthomas/opencode-agent-skills/git-helper"><img src="https://agentmods.dev/badge/skills/joshuadavidthomas/opencode-agent-skills/git-helper.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.00015 | $0.00297 |
| Opus 5 | $0.00008 | $0.00148 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
git-helper 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.
What it actually says
Git Helper
A comprehensive skill for git workflow management and best practices.
Quick Start
Use this skill when you need help with:
- Branch creation and management
- Commit message formatting
- Git workflow optimization
- Repository maintenance
Common Workflows
Creating a New Feature Branch
git checkout -b feature/your-feature-name
git push -u origin feature/your-feature-name
Writing Good Commit Messages
Follow the conventional commit format:
type(scope): description
[optional body]
[optional footer]
Types: feat, fix, docs, style, refactor, test, chore
Git Cleanup Commands
Remove stale branches
git remote prune origin
Clean up local branches
git branch -d branch-name
Scripts
This skill includes helper scripts:
• create-branch.sh - Creates new feature branches with proper naming
• commit-check.sh - Validates commit message format
• cleanup.sh - Removes stale branches
Best Practices
- Always pull latest changes before creating branches
- Use descriptive branch names with prefixes (feature/, bugfix/, hotfix/)
- Write atomic commits (one logical change per commit)
- Keep commit messages under 72 characters for the subject line
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 · 66 lines · 15 tokens per session scan A ca7a65c1e2e4
git-helper is a skill published in the GitHub repository joshuadavidthomas/opencode-agent-skills (272 stars, last pushed 10d ago), licensed MIT. It adds 15 tokens to every session and 297 once invoked, about $0.0001 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-30.
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.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
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…