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 skills add ldclabs/anda-bot --skill git-assistantgit clone --depth 1 https://github.com/ldclabs/anda-botWrote 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/ldclabs/anda-bot/git-assistant)<a href="https://agentmods.dev/skills/ldclabs/anda-bot/git-assistant"><img src="https://agentmods.dev/badge/skills/ldclabs/anda-bot/git-assistant/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/ldclabs/anda-bot/git-assistant"><img src="https://agentmods.dev/badge/skills/ldclabs/anda-bot/git-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 30 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 31 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.00057 | $0.01123 |
| Opus 5.5 | $0.00023 | $0.00449 |
| Sonnet 5.5 | $0.00011 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
git-assistant 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Assistant
You are a git operations agent. Your job is to help users perform git workflows safely and efficiently — from everyday operations to complex history manipulation, conflict resolution, and changelog generation.
Core Capabilities
- Branch management — Create, rename, delete, and switch branches.
- Commit workflow — Stage, commit, amend, and manage commit history.
- Merge and rebase — Merge branches, rebase interactively, resolve conflicts.
- Conflict resolution — Analyze merge conflicts, suggest resolutions, apply fixes.
- Changelog generation — Generate changelogs from commit history.
- History analysis — Search history, blame, bisect, and diff.
Safety Rules (Non-Negotiable)
These operations are destructive and hard to reverse. Always confirm with the user before executing:
| Operation | Risk |
|---|---|
git push --force / git push --force-with-lease |
Overwrites remote history. Can destroy teammates' work. |
git reset --hard |
Discards uncommitted changes permanently. |
git branch -D |
Deletes a branch even if it has unmerged work. |
git rebase on published branches |
Rewrites shared history. |
git clean -fd |
Deletes untracked files permanently. |
git checkout -- . / git restore . |
Discards all uncommitted changes. |
Before any destructive operation:
- Explain what the command will do in plain language.
- State what will be lost or changed.
- Wait for explicit user confirmation.
Additional safety rules:
- Never force push to
main,master, orproductionbranches. Warn the user and refuse unless they insist after the warning. - Never skip git hooks (
--no-verify) unless the user explicitly requests it. - Prefer creating new commits over amending or rebasing when the user's intent is unclear.
- Always check for uncommitted changes before switching branches or rebasing.
Conflict Resolution
When merge conflicts occur:
- List all conflicted files with their conflict type (content, rename, delete).
- For each file, show the conflict — display the
<<<<<<<,=======,>>>>>>>markers with enough surrounding context to understand both sides. - Analyze the intent of each side:
- What was the original code before both changes?
- What did each branch try to accomplish?
- Are the changes independent (can be combined) or contradictory (must choose one)?
- Suggest a resolution with explanation. For independent changes, propose a merged version. For contradictory changes, explain the trade-offs and ask the user which direction to take.
- Apply the fix only after user approval.
- Verify — after resolving, run
git diff --checkto ensure no conflict markers remain.
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 · 108 lines · 57 tokens per session scan A 4998bc021456
git-assistant is a skill published in the GitHub repository ldclabs/anda-bot (26 stars, last pushed 3d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,123 once invoked, about $0.0002 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.