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.
git 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/iot-terminology-boundary)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/iot-terminology-boundary"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/iot-terminology-boundary/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/iot-terminology-boundary"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/iot-terminology-boundary.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00770 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
iot-terminology-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IoT terminology boundary (binding)
The Thing Model (docs/developers/architecture/cross-cutting/foundation/thing-model.md) is the gateway's internal architecture kernel for service / device coordination. Its vocabulary — "Thing", "Shadow", "desired", "reported", "drift" — is internal-only: code, DB column names, developer architecture docs.
User-facing surfaces (admin API responses, UI strings, product docs, error messages, support runbooks) MUST use product terms instead.
Required mapping
| Internal (kernel) | User-facing (product) | Notes |
|---|---|---|
| Thing | node / service / device | Pick the closest concrete noun for the context |
| Shadow | config sync | Or "configuration" when ambient |
| desired (state) | target config | What the admin set |
| reported (state) | applied config | What the device is actually running |
| drift | out of sync | "Drift" is too ML-y for product copy |
| enrollment token | provisioning token | "Enrollment" is OK in admin UI; never in end-user docs |
Where each layer applies
-
Internal-only (Thing/Shadow/desired/reported/drift)
- Go code identifiers + comments under
packages/** - DB column names + Prisma schema
docs/developers/architecture/**architecture documentation- Slog field names (
shadowDesired,shadowReported, etc.) - MQ subject names + audit event types
- Go code identifiers + comments under
-
Product-facing (node / config sync / target / applied / out of sync)
- i18n strings (
packages/{control-plane-ui,agent/ui,ui-shared}/src/i18n/locales/**) - JSX user-visible text
- Admin API response field names + error messages
- Documentation under
docs/users/product/**,docs/users/features/**,docs/operators/ops/runbooks/** - Commit-and-deploy notification copy
- i18n strings (
Why this boundary exists
The Thing Model is borrowed wholesale from IoT vendor patterns (AWS IoT Core, Azure IoT Hub) to keep internal architecture compact and reusable. End-users — admins running Nexus, agent end-users on their laptops — don't share that vocabulary. Surfacing it leaks an implementation detail and creates a learnable-vocabulary gap that competitors don't have.
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.
- 9d ago First seen · 65 lines · 0 tokens per session scan A 00461cfce1be
iot-terminology-boundary is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (23 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 770 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
recipe_author
How to author a recipe in ks-cookbook.
20-phi-redaction-first
PHI redaction first — Presidio gate, token handling, and minimum necessary LLM access for HIPAA workflows.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.