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/znlgis/my-opencode-deepseek-config/git-masternpx skills add znlgis/my-opencode-deepseek-config --skill git-mastergit clone --depth 1 https://github.com/znlgis/my-opencode-deepseek-configWrote 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/znlgis/my-opencode-deepseek-config/git-master)<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/git-master"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/git-master.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.00075 | $0.01294 |
| Opus 5 | $0.00037 | $0.00647 |
| Sonnet 5 | $0.00015 | $0.00259 |
| Haiku 4.5 | $0.00007 | $0.00129 |
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 4d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Master
Advanced Git patterns for when the basics aren't enough.
When to use me
- Rebasing, squashing, or interactive history editing
- Finding when/where code was introduced or deleted (
git blame,git log -S/-G) - Recovering lost commits or branches (
git reflog) - Bisecting to find the commit that introduced a bug
- Cherry-picking or fixup workflows
- Managing stacked branches or worktrees
Atomic commits
One logical change per commit. Before committing, review with:
git add -p # stage hunks interactively — only what belongs together
git diff --cached # review exactly what you're about to commit
If the diff mixes unrelated changes, split them into separate commits.
Rewriting history (safety first)
Never rewrite shared/pushed history unless you own the branch and no one else works on it. For personal branches:
# Interactive rebase — reorder, squash, or edit commits
git rebase -i HEAD~5 # last 5 commits
git rebase -i main # rebase onto main interactively
# Squash the last N commits into one
git reset --soft HEAD~3 # uncommit last 3, keep changes staged
git commit -m "feat: combined feature work"
# Fixup — amend a past commit without a separate "fix" commit
git commit --fixup <sha> # mark this as a fix for <sha>
git rebase -i --autosquash main # automatically reorder+squash fixups
# Amend the last commit (not pushed yet)
git commit --amend --no-edit # add staged changes to last commit
git commit --amend -m "better message"
Code archaeology
Find when code was introduced, changed, or deleted:
# Who last touched each line?
git blame path/to/file -L 40,60 # blame lines 40-60
# When was this string added/removed? (-S = pickaxe)
git log -S "functionName" --oneline -- path/
git log -S "removed_feature" --patch # show the diff that removed it
# When was a regex pattern changed? (-G = grep-based)
git log -G "TODO|FIXME" --oneline
# Find which commit deleted a file
git log --all --full-history -- "**/deleted-file.ts"
# Show a file at a specific point in time
git show <commit>:path/to/file.ts
git show <commit>~1:path/to/file.ts # the version before that commit
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.
- 4d ago First seen · 149 lines · 75 tokens per session scan A 7a2061f1a0cd
git-master is a skill published in the GitHub repository znlgis/my-opencode-deepseek-config (57 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 1,294 once invoked, about $0.0004 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
git-workflow
Use when the task involves Git operations for the public xLLM repository, including choosing branch or tag names, preparing commits and pull requests, backporting fixes, checking repo-specific review expectations, or drafting commit messages from actual diffs.
conventional-commits
Conventional Commits specification for consistent, machine-readable git commit messages. Use when crafting commit messages, enforcing commitlint rules, or generating changelogs/releases.
git-workflow
Branching strategies, conventional commits, PR templates, and merge vs rebase guidance. Activate when starting features, creating PRs, or managing releases.
smart-git-commit
Use this skill for ANY git operation — commits, pushes, PRs, releases, or version tagging. Triggers on: "commit", "push", "save my changes", "create a PR", "open a pull request", "ship this", "make a release", "tag this version", "checkpoint my work", or any request to record or publish code changes. Produces…
git
Unified git workflow for branch-first development: status/diff review, security-first commits, worktrees, and PR creation/review via gh. Auto-activates on: "commit", "push", "branch", "worktree", "pr", "pull request", "merge", "rebase", "git".
crew-commit
Canonical commit workflow for Gas Town crew members: pre-flight checks, branch creation, gt commit with agent identity, push, and PR creation. Use when ready to commit and submit work for review.