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 mrzhangguoguo/oh-my-workbuddy --skill git-mastergit clone --depth 1 https://github.com/mrzhangguoguo/oh-my-workbuddyWrote 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/mrzhangguoguo/oh-my-workbuddy/git-master)<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/git-master"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/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/mrzhangguoguo/oh-my-workbuddy/git-master"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/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.00045 | $0.00794 |
| Opus 5.5 | $0.00018 | $0.00318 |
| Sonnet 5.5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00079 |
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 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ported from oh-my-codex
git-master. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
Git Master
Git operations expert. Use this skill whenever the user needs precise, safe git work: atomic commits, interactive rebasing, branch management, history cleanup, or style-consistent commit messages.
Usage
Invoke the git-master skill and describe the git task, e.g.:
"rebase my feature branch onto main", "squash these 5 commits", "write a conventional
commit for these changes".
Capabilities
- Atomic commits with conventional-commit format
(
feat:,fix:,refactor:,docs:,test:,chore:). - Interactive rebasing (
rebase -i) for reordering, squashing, fixing up. - Branch management: create/rename/delete, branch-point detection, divergence check.
- History cleanup: prune stray commits, rewrite messages, split/join commits.
- Style detection: read the repo's existing commit history to match its convention before writing new commits.
Workflow
-
Assess the working tree. Run read-only checks first:
git status git log --oneline -10 git diff --statDetect the repo's commit style from recent history before composing messages.
-
Plan the operation. For anything destructive (rebase, reset, branch delete, amend of already-pushed commits), use the task list (TaskCreate) to outline steps, and surface a short plan to the user. If the operation rewrites shared/pushed history, ask for explicit confirmation before proceeding (use AskUserQuestion for a clean yes/no).
-
Execute safely.
- Prefer
--autosquashwhen queuing fixups. - For atomic commits, stage narrowly:
git add -por stage specific paths rather thangit add -A. - Write messages that match the detected style; default to Conventional Commits when the repo has no clear convention.
- Prefer
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 · 83 lines · 45 tokens per session scan A 9b6adbd8a3dd
git-master is a skill published in the GitHub repository mrzhangguoguo/oh-my-workbuddy (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 794 once invoked, about $0.0002 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
commit-with-reflection
A Git workflow that creates a Chinese-language report about debugging mistakes, investigation steps, fixes, and lessons learned, then includes that report in a commit. Git is a system for tracking changes to code.
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.
manuscript-as-code
Treat manuscripts as software: version control, reproducible builds, figure pipelines, CI, and structured repo layout. Helps teams avoid 'finalv7' chaos and ensures submission-ready artifacts.