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/bytepine/nexuslink/airulesgit clone --depth 1 https://github.com/bytepine/NexusLinkWrote 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/bytepine/nexuslink/airules)<a href="https://agentmods.dev/rules/bytepine/nexuslink/airules"><img src="https://agentmods.dev/badge/rules/bytepine/nexuslink/airules.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.00026 | $0.01670 |
| Opus 5 | $0.00013 | $0.00835 |
| Sonnet 5 | $0.00005 | $0.00334 |
| Haiku 4.5 | $0.00003 | $0.00167 |
Grade A, and why
AIRules 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 4d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NexusLink AI Workflow (IDE-side Rule)
Division of labor with MCP handshake instructions
- InitializeInstructions (UE handshake): capability routing table, meta-tool constraints, read/write naming.
- This Rule (IDE-side): enforce discover tools → find paths → read/write; forbid guessing cap names/paths; fill project-level
pathFilterprefixes.Source:
Plugins/Developer/NexusLink/Resources/AIRules.mdc— diff generic sections into your project copy after plugin upgrades.
1. Four-step flow (required)
For UE assets / PIE / blueprints / Widget / material / behavior tree / GAS / Lua, call MCP this turn first, then answer:
| Step | Tool | Notes |
|---|---|---|
| 1 Discover capability | search_capabilities |
Skip when cap name is known; otherwise query with 1–2 narrow words (e.g. blueprint graph, runtime actor, behavior tree); no business feature names, asset names, or over-broad single tokens (see §2) |
| 2 Discover asset paths | search_asset |
Requires assetType + functional pathFilter; top-level assets; typed search adds top-level recommendedGet/recommendedManage — prefer those in step 3 |
| 3 Read/write | get_asset_* / manage_asset_* / list_runtime_* etc. |
assetPath only from assets[].path; prefer recommendedGet/recommendedManage; when lists include <k>_defaults, missing fields equal that value ({**defaults,**entry}) |
| 4 Persist | save_asset or manage saveToDisk=true |
Required after disk asset edits; BP/ABP/WBP may also pass compile=true |
Meta-tools search_capabilities, call_capability, submit_feedback must use MCP tools/call directly — not call_capability(capability="search_capabilities", …).
2. Prohibitions
- ❌ Invent a
get_assetaggregate tool (correct:get_asset_<type>, e.g.get_asset_blueprint) - ❌ Search
search_capabilitieswith business terms (ChestPVE,Dice,Attack, etc.) - ❌ Over-broad single-token
search_capabilitiesqueries:blueprint/asset/runtime/animation(causessearch_overflow; add action or subdomain, e.g.blueprint variable,runtime actor) - ❌ Guess
/Game/...paths; noassetType=all+ bare/Game/without filters - ❌ Call
get_asset_*withoutsearch_assetfirst (missingassetPath) - ❌
get_runtime_actor_*/set_runtime_actor_*withoutactorName(calllist_runtime_actorsfirst) - ❌
exec_commandwithout a non-emptycommand - ❌ Runtime Lua tools (
eval_runtime_lua, etc.) without PIE / UnLua ready - ❌ Ignore
_feedbackHint— callsubmit_feedback - ❌ Expect
success:trueon write success (noerrormeans success; only explicitsuccess:falseis failure) - ❌ Pass
assetPaths/actorNames/widgetNamesto capabilities (cross-target viacall_capability.calls[]) - ❌ manage top-level
fields/rows/keys/widgets/opsor bareactionsynthesis (useoperations[]) - ❌ Legacy keys:
blueprintPath/newPath/ownerWidget/filePath/Luapath/classPath(see §3)
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.
- 4d ago First seen · 110 lines · 26 tokens per session scan A 899fe4b7cbd8
AIRules is a cursor rule published in the GitHub repository bytepine/NexusLink (4 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 1,670 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
minimax-m2-core
MiniMax M2.1 agentic-first core behavior: Opus 4.5-style reasoning, 1M context optimization, verification-first development, and production-quality code generation.
monobehaviour-lifecycle
Correct usage of MonoBehaviour lifecycle methods.
visual-scripting-conventions
Best practices for Unity Visual Scripting.
security-best-practices
This rule outlines security considerations for the Rakit UI AI project.
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.