Git AI is a Git extension that records which agent, model, and prompts produced AI-generated code in a repository. It is for developers and teams that need line-level attribution and the surrounding context for code created with AI coding tools. The catalogue skills and instructions support using Git AI in agent-assisted development workflows.
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 git-ai-project/git-ai --skill git-ai-searchgit clone --depth 1 https://github.com/git-ai-project/git-aiWrote 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/git-ai-project/git-ai/git-ai-search)<a href="https://agentmods.dev/skills/git-ai-project/git-ai/git-ai-search"><img src="https://agentmods.dev/badge/skills/git-ai-project/git-ai/git-ai-search/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/git-ai-project/git-ai/git-ai-search"><img src="https://agentmods.dev/badge/skills/git-ai-project/git-ai/git-ai-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.02513 |
| Opus 5.5 | $0.00005 | $0.01005 |
| Sonnet 5.5 | $0.00003 | $0.00503 |
| Haiku 4.5 | $0.00001 | $0.00251 |
Grade A, and why
git-ai-search 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- git-ai-search — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git AI Search Skill
Search and restore AI conversation context from git history using git-ai search and git-ai continue.
Overview
Git AI tracks AI-generated code and the conversations that produced it. This skill helps you:
- Search - Find AI prompt sessions by commit, file, pattern, or author
- Continue - Restore AI session context to continue work where someone left off
- Show - View the full transcript of a specific prompt
When to Use Each Command
| You want to... | Use... |
|---|---|
| See what AI context exists for a commit | git-ai search --commit <sha> |
| See AI context for specific lines | git-ai search --file <path> --lines <range> |
| Read the full AI conversation | git-ai search --commit <sha> --verbose |
| Get machine-readable output | git-ai search --json |
| Find prompts mentioning a topic | git-ai search --pattern "keyword" |
| Continue someone's AI session | git-ai continue --commit <sha> |
| Continue working on a code region | git-ai continue --file <path> --lines <range> |
| Launch Claude with restored context | git-ai continue --commit <sha> --launch |
| View a specific prompt transcript | git-ai show-prompt <id> |
Workflow Patterns
1. Investigate a Commit
Understand what AI assistance was used in a specific commit:
# See a summary of AI sessions in the commit
git-ai search --commit abc1234
# View the full conversations
git-ai search --commit abc1234 --verbose
# Get JSON for programmatic processing
git-ai search --commit abc1234 --json | jq '.prompts | keys[]'
2. Understand a Code Region
Find what AI sessions contributed to specific lines:
# Search by file
git-ai search --file src/main.rs
# Search specific lines
git-ai search --file src/main.rs --lines 100-150
# Multiple line ranges
git-ai search --file src/main.rs --lines 50-75 --lines 200-250
3. Continue Someone's Work
Pick up where a teammate left off:
# See what they were working on
git-ai search --commit abc1234 --verbose
# Restore context and continue in your shell
git-ai continue --commit abc1234
# Or launch directly into Claude Code
git-ai continue --commit abc1234 --launch
# Or copy context to clipboard to paste elsewhere
git-ai continue --commit abc1234 --clipboard
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 · 390 lines · 13 tokens per session scan A 1838416874f4
git-ai-search is a skill published in the GitHub repository git-ai-project/git-ai (2,857 stars, last pushed 5d ago), licensed Apache-2.0. It adds 13 tokens to every session and 2,513 once invoked, about $0.0001 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
remember
Save the decisions, facts, dead ends and architecture this conversation established to Atlas's shared memory, so other agents and future sessions can build on them.
wicked-garden-repo-learn
Learn an unfamiliar repo the way a senior engineer does: follow where the code actually churns, find what that churn touches that the rest of the system leans on, read the load-bearing code for real, then write down BOTH what you learned (knowledge) and what should hold (policies) — as inert estate proposals a human…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
repo-sentinel
Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses. Triggers on: "push to GitHub", "make repo public", "open source this", "is this safe to push", "release audit", "secret leaks".