git-proxy copilot-instructions.md

Project instructions for GitProxy, a service that checks and controls Git pushes before they reach the real remote repository. They summarize the longer AGENTS.md guide for Copilot surfaces with limited space.

In plain words
What is it for?
Use them when changing GitProxy's proxy, service, configuration, interface, authentication, or action-processing code.
Why use it?
They help coding agents preserve approval checks, security rules, processor order, and audit records instead of accidentally bypassing them.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/finos/git-proxy/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/finos/git-proxy

Made for: GitHub Copilot.

Per session 315 This file is loaded in full into every session.
When invoked 315 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00315 $0.00315
Opus 5 $0.00158 $0.00158
Sonnet 5 $0.00063 $0.00063
Haiku 4.5 $0.00032 $0.00032

Measured yesterday against content hash 64af304943c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-proxy copilot-instructions.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 yesterday.

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.

.github/copilot-instructions.md · 16 lines

What it actually says

GitProxy Copilot Instructions

Read AGENTS.md for the full project guide. Use the rules below as the highest-priority summary for Copilot surfaces that truncate long instruction files.

  • Preserve the GitProxy flow: Git HTTP proxy -> ordered action chain -> service API -> audit trail -> approval gate.
  • A push must never reach the real remote unless it is explicitly approved or auto-approved by policy.
  • Do not bypass blockForAuth, waiting-authorization checks, or audit logging.
  • Keep proxy, service, config, and UI responsibilities separate. Do not place policy logic ad hoc in request handlers.
  • The action chain is the core abstraction. Put reusable enforcement logic in processors, organization-specific logic in plugins, and UI/auth state changes in the service layer.
  • Processor order matters. If logic depends on cloned repositories, diffs, or earlier artifacts, place it accordingly.
  • Processors must be idempotent, use the Action object instead of shared mutable state, and preserve audit traceability.
  • Configuration changes must update schema validation, keep backward-compatible defaults, and avoid weakening security by default.
  • Authentication strategies apply to UI and approval workflows. Git push identity is derived from commit metadata, not interactive auth.
  • When changing proxy/processors, test success paths, rejection paths, and audit logging. When changing config, test invalid values and defaults.
  • Use the standard repo commands: npm run build, npm run test, npm run test:e2e, npm run lint, npm run format:check.
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. yesterday First seen · 16 lines · 315 tokens per session scan A 64af304943c4

Subscribe to this mod's changes

git-proxy copilot-instructions.md is an instructions file published in the GitHub repository finos/git-proxy (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 315 tokens to every session, about $0.0016 per session on Opus 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.