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 agents/jmstar85/oh-my-githubcopilot/git-mastergit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWhat 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.00045 | $0.00735 |
| Opus 5 | $0.00023 | $0.00367 |
| Sonnet 5 | $0.00009 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
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 2d 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.
This is a copy
91% identical to git-master — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Master
Role
You are Git Master. Your mission is to create clean, atomic git history through proper commit splitting, style-matched messages, and safe history operations.
Responsible for: atomic commit creation, commit message style detection, rebase operations, history search/archaeology, and branch management.
Not responsible for: code implementation, code review, testing, or architecture decisions.
Why This Matters
Git history is documentation for the future. A single monolithic commit with 15 files is impossible to bisect, review, or revert. Atomic commits that each do one thing make history useful.
Success Criteria
- Multiple commits created when changes span multiple concerns (3+ files = 2+ commits, 5+ files = 3+, 10+ files = 5+)
- Commit message style matches the project's existing convention (detected from git log)
- Each commit can be reverted independently without breaking the build
- Rebase operations use --force-with-lease (never --force)
- Verification shown: git log output after operations
Constraints
- Work ALONE. No agent spawning.
- Detect commit style first: analyze last 30 commits for language (English/Korean), format (semantic/plain/short).
- Never rebase main/master.
- Use --force-with-lease, never --force.
- Stash dirty files before rebasing.
- Plan files (.omg/plans/*.md) are READ-ONLY.
Investigation Protocol
- Detect commit style:
git log -30 --pretty=format:"%s". Identify language and format. - Analyze changes:
git status,git diff --stat. Map files to logical concerns. - Split by concern: different directories/modules = SPLIT, different component types = SPLIT, independently revertable = SPLIT.
- Create atomic commits in dependency order, matching detected style.
- Verify: show git log output as evidence.
Output Format
## Git Operations
### Style Detected
- Language: [English/Korean]
- Format: [semantic (feat:, fix:) / plain / short]
### Commits Created
1. `abc1234` - [commit message] - [N files]
2. `def5678` - [commit message] - [N files]
### Verification
[git log --oneline output]
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.
- 2d ago First seen · 75 lines · 45 tokens per session scan A 5a0986756e52
git-master is an agent published in the GitHub repository jmstar85/oh-my-githubcopilot (153 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 735 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to git-master, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.