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/configuration-architecturegit 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/configuration-architecture)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/configuration-architecture"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/configuration-architecture.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.00000 | $0.00565 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
configuration-architecture 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
Configuration changes — 4-layer model (binding)
Any PR that adds / removes / renames a YAML field, env variable, thing_config_template configKey, system_metadata key, or publisher/receiver wiring MUST conform to the 4-layer model + R1–R5 invariants in docs/developers/architecture/cross-cutting/foundation/configuration-architecture.md.
Read that doc BEFORE editing.
What you MUST do
Adding a new configKey
- Add the constant to
packages/shared/schemas/configkey/(constants +ValidByThingType+TypedRegistry) in the same PR. - Update the
configuration-architecture.md§7 per-key catalog row in the same PR. - Wire the publisher / receiver path per the 4-layer model (see §4 of the doc).
Renaming a YAML field / env var / configKey
- Run
scripts/check-rename.sh OLD NEWas the sweep gate — it covers all 14 layers listed in §6.5 of the architecture doc. - Verify the negative grep returns zero:
git grep -E '\bOLD\b'must be empty before shipping. - Update
.env.exampleand the per-key catalog in the same PR.
Removing a configKey
Hard-delete it when it is internal-only / unshipped; if the config key has shipped to agents, migrate it with a deprecation window (see release-compat-policy.mdc). No @deprecated kept alive, no parallel paths.
What you MUST NOT do
- Add a configKey only to the registry and forget the catalog — admins won't see it, runtime won't recognise it.
- Add a configKey to the catalog only — runtime validation will reject it.
- Add a field to one of
seed.ts/thing_config_template/configreconcilebut not the others — invariants drift silently.
Source of truth
docs/developers/architecture/cross-cutting/foundation/configuration-architecture.md (4-layer model + R1–R5 invariants + §6.5 14-layer rename checklist + §7 per-key catalog).
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 · 47 lines · 0 tokens per session scan A 243b7ce785a7
configuration-architecture is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (23 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 565 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-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.