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 rules/tomasz-tomczyk/crit/proxy-auth-transportgit clone --depth 1 https://github.com/tomasz-tomczyk/critWrote 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/rules/tomasz-tomczyk/crit/proxy-auth-transport)<a href="https://agentmods.dev/rules/tomasz-tomczyk/crit/proxy-auth-transport"><img src="https://agentmods.dev/badge/rules/tomasz-tomczyk/crit/proxy-auth-transport.svg" alt="Measured on agentmods" 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 | $0.00005 | $0.00848 |
| Opus 5 | $0.00003 | $0.00424 |
| Sonnet 5 | $0.00001 | $0.00170 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
proxy-auth-transport scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Direct (non-proxy_auth) browser actions must go through the **local Go server**, never `fetch(shareURL + …)` cross-origin: How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proxy Auth Transport Rules
Rule 1: Both transport modes required
Every CLI command or browser UI action that calls a crit-web API must work in both modes:
- Direct (default): Go server makes HTTP requests with bearer token
- Browser relay (
proxy_auth: true): Browser popup mediates the same API call through an authenticated session
When adding a new crit-web interaction:
- Add the direct HTTP path in Go (share.go or relevant file)
- Add a server endpoint that returns the payload for the popup relay (server.go)
- Add a popup handler in
crit-web/assets/js/share_receiver/handlers.js(note: the directory/route is namedshare_receiver//share-receiver— this describes what the component does (receives share data), whileproxy_authdescribes why it's needed. Both names are correct at their level.) - Add the relay call in
web/app.jsgated onproxy_auth
Rule 2: Relay is transport, not protocol
The popup relay must hit the same crit-web API endpoints with the same payload shapes as the direct path. No relay-specific endpoints on crit-web. The popup handlers are same-origin fetch proxies.
Rule 3: Terminal CLI commands cannot use direct HTTP when proxy_auth is on
When proxy_auth: true (global config), crit-web sits behind an SSO reverse proxy. The terminal cannot complete that auth flow — only the browser can (via the /share-receiver popup relay).
Terminal subcommands that HTTP-call crit-web directly (today: crit share, crit fetch, crit unpublish) must call checkProxyAuthCLIAllowed("crit <cmd>") at the top of their Run* entrypoint and exit with the shared error message. Do not attempt the network call.
Browser UI actions (Share / Pull / Unpublish / Re-share buttons in the review page) must still work: implement both transports per Rule 1 — direct when proxy_auth is false, popup relay when true (web/crit-share.js + crit-web share_receiver/handlers.js).
Direct (non-proxy_auth) browser actions must go through the local Go server, never fetch(shareURL + …) cross-origin:
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 · 53 lines · 5 tokens per session scan A 1bd83fe373e8
proxy-auth-transport is a cursor rule published in the GitHub repository tomasz-tomczyk/crit (979 stars, last pushed 5d ago), licensed MIT. It adds 5 tokens to every session and 848 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
cursorrules
Este repo usa Knowledge-Driven Development (KDD). Las reglas completas para cualquier agente de IA (incluido Cursor) estan en .agents/AGENTS.md — leelo antes de escribir codigo.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.