Nginx多后端路由同步

A routing rule for keeping Nginx, a web server and request router, aligned with several backend services that share the same API path.

In plain words
What is it for?
Use it when adding or changing routes in that API namespace so the matching Nginx configuration is checked and updated.
Why use it?
It prevents requests from being sent to the wrong service when more specific routes are added under /api/wecom/.

Cursor rule

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 rules/nongjun/awesome-harness-engineering/nginx
Clone the repo
git clone --depth 1 https://github.com/nongjun/awesome-harness-engineering
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 587 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00587
Opus 5 $0.00000 $0.00293
Sonnet 5 $0.00000 $0.00117
Haiku 4.5 $0.00000 $0.00059

Measured 2d ago against content hash c8606c3dd9e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Nginx多后端路由同步 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 2d 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.

项目模板/瑞小美AiOS/rules/Nginx多后端路由同步.mdc · 42 lines

What it actually says

Nginx 多后端路由同步

背景

scrm.ireborn.com.cn 的 Nginx 将不同 /api/ 前缀路由到不同后端服务。其中 /api/wecom 被联系人模块(8020)兜底,但内容中心(8003)、门户(8025)、企微托管(8041)也在该命名空间下注册了子路由。此问题已导致三次线上故障。

规则

当在 /api/wecom/ 命名空间下新增或修改路由时:

  1. 必须检查 /etc/nginx/conf.d/scrm.ireborn.com.cn.conf 中是否已有对应的精确 location
  2. 如果没有,必须在 location /api/wecom(联系人兜底)之前添加更具体的 location 规则
  3. Nginx 最长前缀匹配:/api/wecom/media/ 优先于 /api/wecom

当前路由映射

Nginx location 后端 端口
/api/wecom/jsapi-signature 内容中心 8003
/api/wecom/agent-config-signature 内容中心 8003
/api/wecom/oauth-url 内容中心 8003
/api/wecom/verify-token 内容中心 8003
/api/wecom/user-info 内容中心 8003
/api/wecom/oauth-callback 内容中心 8003
/api/wecom/media/ 内容中心 8003
/api/wecom/contact/ 内容中心 8003
/api/wecom/qrcode-login/ 内容中心 8003
/api/wecom/external-contact/ 门户 8025
/api/wecom/internal/ 门户 8025
/api/wecom(兜底) 联系人 8020
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. 2d ago First seen · 42 lines · 0 tokens per session scan A c8606c3dd9e5

Subscribe to this mod's changes

Nginx多后端路由同步 is a cursor rule published in the GitHub repository nongjun/awesome-harness-engineering (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 587 tokens. 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.