Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bug-ops/zephnpx agentmods add skills/bug-ops/zeph/gitWrote 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/bug-ops/zeph/git)<a href="https://agentmods.dev/skills/bug-ops/zeph/git"><img src="https://agentmods.dev/badge/skills/bug-ops/zeph/git/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/bug-ops/zeph/git"><img src="https://agentmods.dev/badge/skills/bug-ops/zeph/git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 153 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 356 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 181 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 428 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00106 | $0.02295 |
| Opus 5.5 | $0.00042 | $0.00918 |
| Sonnet 5.5 | $0.00021 | $0.00459 |
| Haiku 4.5 | $0.00011 | $0.00230 |
Grade A, and why
git 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Operations
Status and Information
git status # working tree status
git status -s # short format
git branch -vv # branches with tracking info
Viewing Changes
# Unstaged / staged / between branches
git diff
git diff --cached
git diff main..feature
# Changes since common ancestor (useful for PRs)
git diff main...feature
# Diff specific file
git diff -- PATH
# Word-level diff
git diff --word-diff
# Stat summary
git diff --stat
# Show a specific commit
git show COMMIT
# Show file at specific commit
git show COMMIT:PATH
Commit History
# Recent commits (compact)
git log --oneline -20
# With diffs
git log -p -5
# Graph view
git log --oneline --graph --all
# With file stats
git log --stat
# Filter by author / date / message / file
git log --author="NAME"
git log --since="2025-01-01" --until="2025-06-01"
git log --grep="fix"
git log -- PATH
# Commits that added/removed a string (pickaxe)
git log -S "function_name"
# Custom format
git log --pretty=format:"%h %ad %s (%an)" --date=short
# Who changed each line
git blame FILE
git blame -L 10,20 FILE
Staging
# Stage specific files
git add FILE1 FILE2
# Stage all tracked file changes
git add -u
# Stage everything (tracked + untracked)
git add -A
# Stage hunks interactively
git add -p
# Unstage file (keep changes)
git reset HEAD FILE
# Discard unstaged changes
git restore FILE
# Restore file from specific commit
git restore --source=COMMIT FILE
Committing
# Commit with message
git commit -m "message"
# Multi-line message
git commit -m "subject" -m "body"
# Stage tracked files and commit
git commit -a -m "message"
# Amend last commit
git commit --amend
# Amend without changing message
git commit --amend --no-edit
# Empty commit (trigger CI)
git commit --allow-empty -m "trigger build"
Undoing Commits
# Revert a commit (creates new inverse commit)
git revert COMMIT
# Revert without auto-commit
git revert --no-commit COMMIT
# Revert a merge commit (keep first parent)
git revert -m 1 MERGE_COMMIT
# Reset to commit (keep changes staged)
git reset --soft COMMIT
# Reset to commit (keep changes unstaged)
git reset --mixed COMMIT
# Reset to commit (discard all changes)
git reset --hard 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.
- 1mo ago First seen · 464 lines · 106 tokens per session scan A 18697a16f0ea
git is a skill published in the GitHub repository bug-ops/zeph (64 stars, last pushed 10d ago), licensed MIT. It adds 106 tokens to every session and 2,295 once invoked, about $0.0004 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-30.
Other skills, from other repositories
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
github
Skill "github" from Hmbown/Codewhale, covering github, when to use, setup, workflow and non-goals.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.