Borrowing it
Nothing to install: this file belongs to sigbit/mcp-auth-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/sigbit/mcp-auth-proxy/main/AGENTS.mdgit clone --depth 1 https://github.com/sigbit/mcp-auth-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/sigbit/mcp-auth-proxy/agents-md)<a href="https://agentmods.dev/instructions/sigbit/mcp-auth-proxy/agents-md"><img src="https://agentmods.dev/badge/instructions/sigbit/mcp-auth-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.
<a href="https://agentmods.dev/instructions/sigbit/mcp-auth-proxy/agents-md"><img src="https://agentmods.dev/badge/instructions/sigbit/mcp-auth-proxy/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.00528 | $0.00528 |
| Opus 5.5 | $0.00211 | $0.00211 |
| Sonnet 5.5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
mcp-auth-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 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
main.go: CLI entry for the proxy.pkg/mcp-proxy: Server wiring (routing, TLS, startup/shutdown).pkg/auth: OAuth/OIDC/password providers and auth routes (templates/).pkg/backend: Stdio→HTTP bridge and transparent HTTP/S backends.pkg/proxy: Reverse proxy and header injection.pkg/repository: Lightweight KVS persistence.pkg/utils: Keys, randomness, logging helpers.docs/: Docusaurus site for product docs.
Build, Test, and Development Commands
- Build:
go build -o bin/mcp-auth-proxy .— compile the binary. - Test:
go test ./...— run unit tests. - Coverage:
go test ./... -coverprofile=coverage.out && go tool cover -html=coverage.out -o coverage.html.
Coding Style & Naming Conventions
- Language: Go 1.22+ modules (
go.mod). - Formatting:
gofmt -s -w .(CI checks formatting);go fmt ./...locally. - Packages: lower-case names; exported identifiers use PascalCase; files
*_test.gofor tests. - Imports: standard → third-party → local (
github.com/sigbit/mcp-auth-proxy/v2/...).
Testing Guidelines
- Framework: Go
testingpackage (*_test.go). - Scope: Test auth providers, proxy behavior, and backend adapters in
pkg/.... - Naming:
TestXxxwith table-driven tests where useful. - Run all:
go test ./...; target a package:go test ./pkg/proxy -v.
Commit & Pull Request Guidelines
- Commits: Conventional Commits (feat, fix, docs, refactor, perf, test, build, ci, chore, revert). Example:
feat: add GitHub OAuth provider support. - PRs: use
.github/pull_request_template.mdas the template; include a clear description, linked issues (Fixes #123), reproduction steps, and before/after notes. Include config snippets for new flags or env vars. - CI: ensure
gofmtpasses and tests are green.
Security & Configuration Tips
- Set
EXTERNAL_URLcorrectly; accept TLS TOS with--tls-accept-toswhen auto-TLS is detected. - Avoid committing contents of
data/(runtime-only).
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 · 44 lines · 528 tokens per session scan A 959938804b23
mcp-auth-proxy AGENTS.md is an instructions file published in the GitHub repository sigbit/mcp-auth-proxy (183 stars, last pushed 5mo ago), licensed MIT. It adds 528 tokens to every session, about $0.0021 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.