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 instructions/jonathanabila/git-override/agents-mdgit clone --depth 1 https://github.com/jonathanabila/git-overrideWhat 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.05231 | $0.05231 |
| Opus 5 | $0.02616 | $0.02616 |
| Sonnet 5 | $0.01046 | $0.01046 |
| Haiku 4.5 | $0.00523 | $0.00523 |
Grade C, and why
git-override AGENTS.md scanned grade C with 2 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
2. **Curl**: `curl ... | bash` downloads hooks directly to `.git/hooks/` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **Curl**: `curl ... | bash` downloads hooks directly to `.git/hooks/` How it starts
The opening of the file, as written. The whole thing — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions for git-local-override
This document provides guidelines for AI agents working on the git-local-override project.
Project Overview
git-local-override is a bash-based tool that allows users to maintain local modifications to git-tracked files without committing them. It uses git hooks to transparently manage file content based on recursive config files (.local-overrides.yaml) in the repository.
Repository Structure
git-local-override/
├── bin/ # Executable CLI tool
│ └── git-local-override # Main command-line interface
├── hooks/ # Git hook scripts
│ ├── local-override-lib.sh # Shared library functions
│ ├── local-override-filter-smudge # Smudge filter (checkout)
│ ├── local-override-filter-clean # Clean filter (staging)
│ ├── local-override-post-checkout
│ ├── local-override-pre-rebase
│ ├── local-override-pre-commit
│ └── local-override-post-commit
├── shared/ # Shared shell modules
│ ├── local-override-resolver.sh # Canonical recursive config resolver
│ └── local-override-shell-init.sh # Shell wrapper source (printed by shell-init)
├── scripts/ # Installation and release scripts
│ ├── install.sh
│ ├── uninstall.sh
│ ├── pin-manifest.sh # Shared pin-file list (release.sh + check-docs-sync.sh)
│ └── release.sh # Changelog release prep helper
├── tests/ # Test suite
│ ├── run-tests.sh # Main test runner (unit suite)
│ ├── run-docker.sh # Docker test launcher
│ ├── test-lib.sh # Shared assertion harness (info/pass/fail, counters)
│ ├── coverage.sh # kcov entrypoint (opt-in coverage run)
│ ├── bench-filter-process.sh # filter.process benchmark + roundtrip harness
│ ├── docker/ # Docker test infrastructure
│ │ ├── Dockerfile # Ubuntu test image
│ │ ├── Dockerfile.bash3 # Bash 3.2 compatibility image
│ │ └── entrypoint.sh
│ └── integration/ # Integration tests
│ ├── test-install.sh # Install/uninstall tests
│ ├── test-git-ops.sh # Git operations tests
│ ├── test-precommit.sh # Pre-commit framework tests
│ └── test-worktrees.sh # Linked-worktree tests
├── .github/ # GitHub configuration
│ ├── workflows/
│ │ ├── test.yml # CI test workflow
│ │ └── release.yml # Tag-triggered GitHub release publish
│ ├── ISSUE_TEMPLATE/ # Issue templates
│ ├── PULL_REQUEST_TEMPLATE.md
│ ├── CODEOWNERS
│ └── dependabot.yml
├── docs/ # Additional documentation (DESIGN.md, rebase-regression-tdd-plan.md)
├── plans/ # Implementation plans + index (plans/README.md)
├── Formula/ # Draft Homebrew formula (unpublished)
│ └── git-local-override.rb
├── AGENTS.md # Canonical agent instructions (this file)
├── CLAUDE.md # Symlink -> AGENTS.md
├── VERSION # Release version file (synced by scripts/release.sh)
├── .pre-commit-hooks.yaml # Pre-commit integration definitions
├── .pre-commit-config.yaml # Pre-commit hooks for this repo
├── .editorconfig # Editor configuration
├── .gitattributes # Line ending configuration
├── Makefile # Build automation
├── README.md # User documentation
├── CONTRIBUTING.md # Contributor guidelines
├── CHANGELOG.md # Version history
├── SECURITY.md # Security policy
├── CODE_OF_CONDUCT.md # Contributor code of conduct
└── LICENSE # MIT license
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.
- 2d ago First seen · 507 lines · 5,231 tokens per session scan C 5a62b589f755
git-override AGENTS.md is an instructions file published in the GitHub repository jonathanabila/git-override (5 stars, last pushed 1mo ago), licensed MIT. It adds 5,231 tokens to every session, about $0.0262 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.