git-proxy: Instructions file for Codex

AGENTS.md

git-proxy AGENTS.md is an instructions file for Codex, OpenCode from finos/git-proxy. It costs 2,025 tokens per session, scanned A, original, Apache-2.0.

A project guide for GitProxy, a Git HTTP proxy that checks code changes before sending them to the real Git server. It documents the project structure, tools, commands, and main components.

In plain words
What is it for?
Use it when working on GitProxy, including its proxy server, processing chain, service API, database, or web interface, and when running its build, unit tests, end-to-end tests, or checks.
Why use it?
It gives a coding agent the repository context needed to build, run, test, lint, and format GitProxy correctly. GitProxy is software that can enforce policies and require approval before accepting pushes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is finos/git-proxy's own configuration. It tells Codex and OpenCode how to work on git-proxy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything git-proxy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to finos/git-proxy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/finos/git-proxy/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/finos/git-proxy

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for git-proxy AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/finos/git-proxy/agents-md/github.svg)](https://agentmods.dev/instructions/finos/git-proxy/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/finos/git-proxy/agents-md"><img src="https://agentmods.dev/badge/instructions/finos/git-proxy/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.

agentmods 80×15 button for git-proxy AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/finos/git-proxy/agents-md"><img src="https://agentmods.dev/badge/instructions/finos/git-proxy/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,025 This file is loaded in full into every session.
When invoked 2,025 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02025 $0.02025
Opus 5.5 $0.00810 $0.00810
Sonnet 5.5 $0.00405 $0.00405
Haiku 4.5 $0.00202 $0.00202

Measured 20d ago against content hash faf7b32b546d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-proxy 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 20d 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.

AGENTS.md · 409 lines

How it starts

The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — GitProxy

Project Overview

GitProxy is a Git HTTP proxy that intercepts Git operations (primarily git push) and enforces organizational policies before allowing changes to reach the actual Git host.

It acts as:

  • A policy enforcement engine (via processors and plugins)
  • A review/approval gate (manual or automated)
  • A proxy server for Git operations
  • A UI + API layer for reviewing, approving, and auditing pushes

The core design principle is a chain-of-processors architecture where each Git action flows through ordered processing steps.


Build & Run

# Build
npm run build

# Run unit tests
npm run test

# Run e2e tests
npm run test:e2e

# Lint check/fix
npm run lint
npm run lint:fix

# Format check/fix
npm run format:check
npm run format

Stack: TypeScript, Node >=22, Express 5, React 16, Vitest 3, NeDB / MongoDB


High-Level Architecture

GitProxy consists of four main components:

Contributor (git push)
   ↓
HTTP Proxy (/src/proxy)
   ↓
Action Chain (Processors + Plugins)
   ↓
Service API (/src/service)
   ↓
Database (audit, users, repos, approvals)
   ↓
Web UI (/src/ui)

1. Proxy Server (/src/proxy)

Express-based HTTP proxy that:

  • Intercepts Git operations
  • Parses requests into an Action
  • Executes the appropriate Action Chain
  • Blocks, rejects, or queues for approval

Core concepts:

  • Action — Represents a Git operation (push/pull/default)
  • Chain — Ordered list of processors
  • Processor (Step) — A single policy enforcement unit
  • Plugin — Custom processor injected externally

2. Service API (/src/service)

Express application responsible for:

  • UI communication
  • Authentication (Passport strategies)
  • Database access
  • Approval/rejection workflows

Default port: 8080

Authentication strategies supported:

  • Local
  • ActiveDirectory
  • OpenID Connect

3. Configuration (/src/config)

Loads and validates proxy.config.json.

Controls:

Read the full file on GitHub · 409 lines

Changes

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.

  1. 20d ago Changed · +4 lines · +84 tokens per session faf7b32b546d
  2. 1mo ago Changed · +1 lines · +5 tokens per session d52c788f07d3
  3. 1mo ago First seen · 404 lines · 1,936 tokens per session scan A f04afcef2592

Subscribe to this mod's changes

git-proxy AGENTS.md is an instructions file published in the GitHub repository finos/git-proxy (262 stars, last pushed today), licensed Apache-2.0. It adds 2,025 tokens to every session, about $0.0081 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.

Related

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).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens