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/alphabitcore/nexus-gateway/release-compat-policygit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWrote 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/alphabitcore/nexus-gateway/release-compat-policy)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/release-compat-policy"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/release-compat-policy.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.00366 | $0.00366 |
| Opus 5 | $0.00183 | $0.00183 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
release-compat-policy 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 5d 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
Release policy (1.0 GA): backward compatibility for shipped contracts (binding)
The gateway is at 1.0 GA — it has released users and downstream services.
Rules
- Shipped contracts must stay backward compatible. Any change to an
externally shipped contract — public/OSS + admin API (OpenAPI), agent↔Hub
wire protocol,
packages/shared/API once in a released agent binary, persisted DB schema, config-key / shadow /system_metadatakeys, audit /traffic_eventshape — must preserve backward compatibility OR ship a versioned migration + deprecation window. Never a silent break. - Breaking a shipped contract requires a major-version bump plus a
CHANGELOG.mdmigration note describing the upgrade path. - Internal-only code stays greenfield. Private functions, un-shipped packages, tests, and dev-only seed/records: delete dead code outright, no parallel "legacy" paths kept for their own sake.
- Discriminator: has this contract shipped to a user or another service? — yes → migrate with a compat path; no → greenfield.
Post-1.0 work is predominantly additive: new provider adapters, new spec coverage, improvements behind stable contracts.
Why
At GA we owe migration paths to real users and services. A silent break to a shipped contract is a production incident; an aggressive internal refactor behind a stable contract is free. Keep the two straight.
Skipping this rule requires explicit user approval in chat.
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.
- 5d ago First seen · 36 lines · 366 tokens per session scan A f1cf013b7d9b
release-compat-policy is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (23 stars, last pushed 3d ago), licensed Apache-2.0. It adds 366 tokens to every session, about $0.0018 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-30.
Other cursor rules, from other repositories
10-deterministic-audit
Enforce deterministic audit behavior — no invented controls, cite authoritative sources, emit traceable artifacts.
flagship_author
How to author a flagship in ks-cookbook.
recipe_author
How to author a recipe in ks-cookbook.
30-framework-routing
Route tasks to HIPAA, HITECH, PCI-DSS, SOC 2, ISO 27001, NIST CSF, NIST AI RMF, FERPA, COPPA, CCPA, US state privacy, GDPR, FedRAMP, SOX, CMMC, and GLBA skills based on user intent and presets.
00-compliance-agent-core
Core compliance agent mission, PHI redaction gate, and audit lifecycle for HIPAA, PCI-DSS, and SOC 2.
20-phi-redaction-first
PHI redaction first — Presidio gate, token handling, and minimum necessary LLM access for HIPAA workflows.