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/jmylchreest/aide/gitnpx skills add jmylchreest/aide --skill gitgit clone --depth 1 https://github.com/jmylchreest/aideWrote 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/jmylchreest/aide/git)<a href="https://agentmods.dev/skills/jmylchreest/aide/git"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/git.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.00008 | $0.01076 |
| Opus 5 | $0.00004 | $0.00538 |
| Sonnet 5 | $0.00002 | $0.00215 |
| Haiku 4.5 | $0.00001 | $0.00108 |
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 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Mode
Recommended model tier: balanced (sonnet) - this skill performs straightforward operations
Expert git operations including worktree management for parallel work.
Commit Guidelines
Message Format
<type>: <short description>
[optional body]
Types: feat, fix, refactor, docs, test, chore
Commit Process
- Check status:
git status - Review diff:
git diff - Stage specific files (not
git add .) - Write descriptive message
- Never skip hooks unless explicitly asked
Worktree Management
Create Worktree
# For feature work
git worktree add ../feature-branch -b feature/name
# For parallel tasks
git worktree add ../aide-worktrees/task-1 -b aide/task-1
List Worktrees
git worktree list
Remove Worktree
git worktree remove ../feature-branch
git branch -d feature/name # if merged
Common Operations
Feature Branch Workflow
git checkout -b feature/name
# ... work ...
git add <specific-files>
git commit -m "feat: add feature"
git push -u origin feature/name
Rebase onto Main
git fetch origin
git rebase origin/main
# resolve conflicts if any
git push --force-with-lease
Cherry-Pick
git cherry-pick <commit-hash>
Stash
git stash push -m "description"
git stash list
git stash pop
Safety Rules
Never run without explicit user request:
git push --force(use--force-with-leaseif needed)git reset --hardgit clean -fgit checkout .orgit restore .
Safe operations:
git status,git diff,git loggit add <specific-files>git commitgit push(without force)git worktreeoperations
Failure Handling
Commit failures:
- Pre-commit hook failure - Read the error, fix the issue, create NEW commit (never amend after hook failure)
- Merge conflict - Report conflicts, do not auto-resolve without explicit request
- Push rejected - Fetch and rebase, report if conflicts arise
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 · 192 lines · 8 tokens per session scan A d9c894506941
git is a skill published in the GitHub repository jmylchreest/aide (16 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 1,076 once invoked, about $0.0000 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
alipay-webhooks
Receive and verify Alipay (Antom / Alipay+) webhook notifications. Use when setting up Alipay webhook handlers, debugging RSA256 Signature header verification, or handling payment events like notifyPayment, notifyCapture, notifyRefund, notifyAuthorization, and notifyDispute.
clio-webhooks
Receive and verify Clio (Clio Manage) webhooks. Use when setting up Clio webhook handlers, debugging X-Hook-Signature verification, completing the X-Hook-Secret handshake, or handling legal practice events like matter.created, contact.updated, activity.created, or bill events.