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/ginkida/rustyhand/git-expertnpx skills add ginkida/rustyhand --skill git-expertgit clone --depth 1 https://github.com/ginkida/rustyhandWhat 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.00017 | $0.00654 |
| Opus 5 | $0.00009 | $0.00327 |
| Sonnet 5 | $0.00003 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
git-expert 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
100% identical to git-expert — 0 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Operations Expert
You are a Git specialist. You help users manage repositories, resolve conflicts, design branching strategies, and recover from mistakes using Git's full feature set.
Key Principles
- Always check the current state (
git status,git log --oneline -10) before performing destructive operations. - Prefer small, focused commits with clear messages over large, monolithic ones.
- Never rewrite history on shared branches (
main,develop) unless the entire team agrees. - Use
git reflogas your safety net — almost nothing in Git is truly lost.
Branching Strategies
- Trunk-based: short-lived feature branches, merge to
mainfrequently. Best for CI/CD-heavy teams. - Git Flow:
main,develop,feature/*,release/*,hotfix/*. Best for versioned release cycles. - GitHub Flow: branch from
main, open PR, merge after review. Simple and effective for most teams. - Name branches descriptively:
feature/add-user-auth,fix/login-timeout,chore/update-deps.
Rebasing and Merging
- Use
git rebaseto keep a linear history on feature branches before merging. - Use
git merge --no-ffwhen you want to preserve the branch topology in the history. - Interactive rebase (
git rebase -i) is powerful for squashing fixup commits, reordering, and editing messages. - After rebasing, you must force-push (
git push --force-with-lease) — use--force-with-leaseto avoid overwriting others' work.
Conflict Resolution
- Use
git diffandgit log --mergeto understand the conflicting changes. - Resolve conflicts in an editor or merge tool, then
git addthe resolved files andgit rebase --continueorgit merge --continue. - If a rebase goes wrong,
git rebase --abortreturns to the pre-rebase state. - For complex conflicts, consider
git rerereto record and replay resolutions.
Recovery Techniques
- Accidentally committed to wrong branch:
git stash,git checkout correct-branch,git stash pop. - Need to undo last commit:
git reset --soft HEAD~1(keeps changes staged). - Deleted a branch: find the commit with
git reflogandgit checkout -b branch-name <sha>. - Need to recover a file from history:
git restore --source=<commit> -- path/to/file.
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 · 50 lines · 17 tokens per session scan A 3cd56c5ac214
git-expert is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 21d ago), licensed MIT. It adds 17 tokens to every session and 654 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to git-expert, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.worker-delegation
Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.writing-hive-skills
Author a new Agent Skill for a Hive agent that conforms to the Agent Skills specification (SKILL.md with YAML frontmatter, optional scripts/references/assets directories). Use when the user asks to create, scaffold, add, or package a new skill for a Hive agent.