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.
Borrowing it
Nothing to install: this file belongs to git-ai-project/git-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/git-ai-project/git-ai/main/AGENTS.mdgit 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/instructions/git-ai-project/git-ai/agents-md)<a href="https://agentmods.dev/instructions/git-ai-project/git-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/git-ai-project/git-ai/agents-md/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/instructions/git-ai-project/git-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/git-ai-project/git-ai/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.04598 | $0.04598 |
| Opus 5.5 | $0.01839 | $0.01839 |
| Sonnet 5.5 | $0.00920 | $0.00920 |
| Haiku 4.5 | $0.00460 | $0.00460 |
Grade A, and why
git-ai AGENTS.md 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Non-Negotiable Rules
These are hard constraints. Violating any of them will get a PR rejected outright.
-
All Git integration/processing is trace2-driven -- we do NOT wrap git. All git command processing is based on trace2, so EVERYTHING we do must be fully async. As a result, we cannot rely on repo/git state at processing time being reflective of the state whenever the given operation actually occurred. We have a highly latency-sensitive trace2 ingestion flow that gathers/estimates the minimal possible state and orders events for later async processing.
-
No new work on the critical ingestion path. You CANNOT add git spawns, git object lookups, ref checks, etc. in the critical ingestion path of the daemon. It is EXTREMELY latency-sensitive -- even additional file reads have meaningful overhead on this path, which is sensitive to sub-millisecond latency increases.
-
No non-constant-time git work anywhere. You CANNOT add git spawns, git object lookups, ref checks, etc. that are not constant-time (e.g., must be O(2)/O(3), not O(n)). You cannot have any operation that calls git per commit, per file, per object, or per ref -- that is not constant time. You can still call git outside of latency-sensitive paths, but instead of calling it once per item, find a constant-time alternative: a plumbing command, a command that accepts batched inputs, etc., so you avoid the massive overhead of N process spawns. Rule of thumb: if you're calling git or looking up objects/refs "for each
<thing>," you're doing it wrong. -
Unbounded git spawns are an automatic rejection. Changes/PRs with unbounded git spawns will NOT be accepted.
-
Reuse existing code. This is a large codebase. For nearly any operation you need, there is almost certainly a helper function already available and tested. Reuse code as much as practical -- it also keeps diffs small. PRs that fail to reuse existing code where applicable will be rejected immediately.
-
Follow STRICT TDD. PRs that are not clearly TDD-driven with high-quality
TestRepo-based tests will be rejected immediately.
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 Changed · +39 tokens per session 55af78277b4e
- 2mo ago First seen · 249 lines · 4,559 tokens per session scan A ce8e337ce010
git-ai AGENTS.md is an instructions file published in the GitHub repository git-ai-project/git-ai (2,944 stars, last pushed yesterday), licensed Apache-2.0. It adds 4,598 tokens to every session, about $0.0184 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.
git-ai AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| git-ai AGENTS.mdgit-ai-project/git-ai | Instructions file | 2.9k | yesterday | Apache-2.0 | A | 4,598 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | today | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | yesterday | MIT | A | 4,680 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 5,516 | GitHub Copilot |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 3,093 | GitHub Copilot |
| deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness | Instructions file | 274k | 2d ago | MIT | A | 4,313 | Codex, OpenCode |