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/ui-shared-boundarygit 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/ui-shared-boundary)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/ui-shared-boundary"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/ui-shared-boundary.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.00462 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
ui-shared-boundary 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.
What it actually says
packages/ui-shared boundary (binding)
packages/ui-shared is the cross-bundle library used by both the Control Plane UI and the Agent Dashboard. It MUST be a leaf in the import graph from each consumer's perspective.
Once ui-shared reaches into either consumer, it stops being shareable.
Allowed
control-plane-ui→ui-shared✓agent/ui/frontend→ui-shared✓ui-shared→ external packages (react,react-i18next,recharts, etc.) ✓
Forbidden
ui-shared→control-plane-ui✗ui-shared→agent/ui/frontend✗ui-shared→agent/cmd/...✗ui-shared→ anything outsideui-shared/(other than vetted externals) ✗
What ui-shared MAY contain
- Layer 1 + Layer 2 design tokens.
- Pure presentation components (
Button,Input,Select,Toast,Modal). - Recharts wrappers +
chartColors.ts. - Shared i18n namespace.
- Theme hooks (
useTheme,useChartColors). - Format helpers (
formatNumber,formatDate,formatBytes).
What ui-shared MUST NOT contain
- API clients / fetchers.
- Routing.
- Context providers that import from a specific bundle.
- State management stores.
- Business logic (
submitRoutingRule,enrollAgent).
Enforcement
npm run check:ui-shared-boundary
The lint scans packages/ui-shared/src/ imports for forbidden source paths. Non-strict mode warns; --strict fails CI.
Source
docs/developers/architecture/cross-cutting/ui/ui-shell-architecture.md is the canonical doc. Read before adding code to ui-shared.
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.
- 3d ago First seen · 56 lines · 0 tokens per session scan A 3d645c6dbdb1
ui-shared-boundary is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (22 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 462 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.