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/redhatinsights/uhc-auth-proxy/agents-mdgit clone --depth 1 https://github.com/RedHatInsights/uhc-auth-proxyWhat 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.01125 | $0.01125 |
| Opus 5 | $0.00562 | $0.00562 |
| Sonnet 5 | $0.00225 | $0.00225 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
uhc-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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides orientation for AI agents and contributors working on uhc-auth-proxy. For project purpose and usage, see README.md. For domain-specific rules, see the guideline files below.
Guideline Documents
| File | Scope |
|---|---|
| docs/security-guidelines.md | Token handling, user-agent validation, credential flow, and secrets management |
| docs/performance-guidelines.md | In-memory cache behavior, shared HTTP client, mutex patterns, and Prometheus metrics |
| docs/error-handling-guidelines.md | Custom error types (HttpError, AccountError), wrapping conventions, and status code propagation |
| docs/api-contracts-guidelines.md | Endpoint contracts, accepted user-agents, and identity payload shape |
| docs/testing-guidelines.md | Ginkgo v2 / Gomega conventions, test wrappers, and cache clearing between tests |
| docs/integration-guidelines.md | External HTTP call patterns, UHC account management API interaction, and the client.Wrapper interface |
Repository Layout
main.go # Entrypoint -- delegates to cmd.Execute()
cmd/
root.go # Cobra root command, Viper config init
start.go # `start` subcommand -- launches the HTTP server
run.go # `run` subcommand -- CLI one-shot identity fetch
server/
server.go # chi router, middleware stack, RootHandler, Prometheus counters
cache/
cache.go # In-memory TTL cache (2-hour expiry, mutex-guarded)
requests/
client/
wrapper.go # HTTPWrapper / Wrapper interface -- all outbound HTTP
access.go # SSO token refresh with mutex-guarded caching
config.go # Viper defaults for ACCESS_TOKEN_URL, TIMEOUT_SECONDS
types.go # HttpError type
cluster/
cluster.go # GetIdentity / GetCurrentAccount facade
types.go # Registration, Account, Identity, test fakes
config.go # Viper defaults for UHC API URLs
logger/
logger.go # zap JSON logger with optional CloudWatch tee
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.
- 3d ago First seen · 81 lines · 1,125 tokens per session scan A 1138d5e2f48a
uhc-auth-proxy AGENTS.md is an instructions file published in the GitHub repository RedHatInsights/uhc-auth-proxy (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,125 tokens to every session, about $0.0056 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-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.