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.
curl -O https://raw.githubusercontent.com/finos/git-proxy/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/finos/git-proxyWrote 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/finos/git-proxy/copilot-instructions)<a href="https://agentmods.dev/instructions/finos/git-proxy/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/finos/git-proxy/copilot-instructions/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/finos/git-proxy/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/finos/git-proxy/copilot-instructions.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.00315 | $0.00315 |
| Opus 5.5 | $0.00126 | $0.00126 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
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 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.
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
Actionobject 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.
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 · 16 lines · 315 tokens per session scan A 64af304943c4
git-proxy copilot-instructions.md is an instructions file published in the GitHub repository finos/git-proxy (262 stars, last pushed today), licensed Apache-2.0. It adds 315 tokens to every session, about $0.0013 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 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).
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.
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).
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 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).
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.