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/ashish7802/awesome-api-skills/gitnpx skills add ashish7802/awesome-api-skills --skill gitgit clone --depth 1 https://github.com/ashish7802/awesome-api-skillsWrote 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/ashish7802/awesome-api-skills/git)<a href="https://agentmods.dev/skills/ashish7802/awesome-api-skills/git"><img src="https://agentmods.dev/badge/skills/ashish7802/awesome-api-skills/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.00000 | $0.00422 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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.
What it actually says
Git Skill
Distributed version control system.
Ecosystem Graph
graph LR
git["Git"]
git -- "works well with" --> github-actions
Quick Start
Git tracks changes in source code during software development.
git init
git commit -m "Initial commit"
Production Patterns
Interactive Rebase
Before merging a feature branch into main, use git rebase -i main to squash messy "WIP" commits into clean, atomic, descriptive commits that clearly outline the feature's history.
Architecture & Scaling
Branching Strategies
Trunk-Based Development (short-lived feature branches merging into main quickly) is preferred over long-lived GitFlow branches to prevent massive, unresolvable merge conflicts.
Error Recovery
If you accidentally commit secrets, using git rm is not enough as the secret remains in history. Use git filter-repo or BFG Repo-Cleaner to permanently scrub the file from all historical commits, and invalidate the secret immediately.
Security Notes
Sign your commits using GPG or SSH keys. Platforms like GitHub verify these signatures, assuring team members that the commit wasn't spoofed.
Relationships
Works Well With: github-actions
References
Why use this skill
Use this when your agent works with git — structured patterns beat pasted docs and prevent common hallucinations.
AI pitfalls
- Referencing CLI flags or config keys that do not exist
- Using outdated major versions of tools
- Skipping lockfile or version pinning in examples
Production checklist
- Secrets in environment variables, not source code
- Error handling and logging in place
- Rate limits and timeouts configured
Related skills
github-actions— works well with
Last Verified: 2026-07-02
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 59 lines · 0 tokens per session scan A 2e964acf6370
git is a skill published in the GitHub repository ashish7802/awesome-api-skills (13 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 422 tokens. 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
claude-api-cost-optimization
Save 50-90% on Claude API costs with Batch API, Prompt Caching & Extended Thinking. Official techniques, verified.
integrations
NextDNS integration guides for third-party platforms and services. This skill should be used when integrating NextDNS with routers, home automation systems, network management platforms, or other third-party services. It also guides transport selection across DoH, DoT, DoQ, DoH3, IPv6, and legacy DNS. Triggers on…
nextdns-cli
NextDNS CLI client best practices for installation, configuration, and management of DNS-over-HTTPS proxy. This skill should be used when installing NextDNS on routers, servers, or client devices, configuring DNS settings, managing the daemon, or troubleshooting DNS issues. Triggers on tasks involving NextDNS CLI…
nextdns-ui
NextDNS Web UI configuration and management best practices. This skill should be used when configuring NextDNS profiles via the web interface (my.nextdns.io), including security features, privacy lists, parental controls, and monitoring logs.
nextdns-frontend
Frontend integration for the NextDNS API using Nuxt 4, Next.js 16, Astro, SvelteKit, or React Router v8. This skill covers secure API key proxying via the BFF pattern, profile management UI, real-time SSE log streaming, analytics chart data preparation, and error handling. Use this skill when building a custom NextDNS…
nextdns-api
NextDNS API integration best practices for authentication, profile management, analytics, logs, and real-time streaming. This skill should be used when working with NextDNS API endpoints, handling DNS analytics, managing security profiles, or implementing DNS filtering solutions. Triggers on tasks involving NextDNS…