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/stramp/lost-mines-phandelver/unreal-engine-cppgit clone --depth 1 https://github.com/Stramp/Lost-Mines-PhandelverWhat 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.01296 |
| Opus 5 | $0.00000 | $0.00648 |
| Sonnet 5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
unreal-engine-cpp 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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C++ Code Conventions - Unreal Engine 5.7
Naming (CRITICAL)
- Classes: PascalCase with appropriate prefix:
Afor Actors (ex:AMyProject2Character,APlayerController)Ufor UObjects (ex:UMyGameInstance,UMyComponent)Ffor Structs (ex:FPlayerStats,FWeaponData)Efor Enums (ex:EPlayerState,EWeaponType)Ifor Interfaces (ex:IInteractable,IDamageable)Tfor Templates (ex:TArray,TMap,TSet)
- Functions: PascalCase (ex:
BeginPlay(),Tick(),OnHit()) - Variables: PascalCase with prefixes:
- Booleans:
b(ex:bIsRunning,bIsActive,bHasWeapon) - Floats: no prefix (ex:
Health,MaxHealth,Speed) - Integers: no prefix (ex:
AmmoCount,Level) - Enums:
E(ex:EPlayerState CurrentState) - Interfaces:
I(ex:IInteractable* InteractableObject)
- Booleans:
- Constants:
constwith PascalCase (ex:const float MaxSpeed = 1000.0f;)
Macros and Annotations (ESSENTIAL)
- ALWAYS use Unreal macros for classes:
UCLASS()for classes that inherit fromUObjectUSTRUCT()for structsUENUM()for enumsUINTERFACE()for interfaces
- UPROPERTY() - Use for:
UPROPERTY(BlueprintReadWrite)- Read/write in BlueprintUPROPERTY(BlueprintReadOnly)- Read-only in BlueprintUPROPERTY(VisibleAnywhere)- Visible in editor, not editableUPROPERTY(EditAnywhere)- Editable in editorUPROPERTY(EditDefaultsOnly)- Editable only in defaultsUPROPERTY(EditInstanceOnly)- Editable only in instancesUPROPERTY(Replicated)- Network replication
- UFUNCTION() - Use for:
UFUNCTION(BlueprintCallable)- Callable from BlueprintUFUNCTION(BlueprintImplementableEvent)- Implemented in BlueprintUFUNCTION(BlueprintNativeEvent)- Default implementation in C++, can be overridden in BlueprintUFUNCTION(Server, Reliable)- Server RPCUFUNCTION(Client, Reliable)- Client RPC
Headers and Includes
- ALWAYS use
#include "CoreMinimal.h"at the top of .cpp files - Use
#pragma oncein all headers (don't use include guards) - Use forward declarations in headers when possible:
// In header (.h) class APlayerController; class UWidget; // In cpp #include "PlayerController.h" #include "Components/Widget.h" - Organize includes in this order:
- Corresponding header (ex:
#include "MyClass.h") - Engine headers (ex:
#include "Engine/Engine.h") - Project headers
- Plugin headers
- STL (avoid when possible)
- Corresponding header (ex:
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.
- 2d ago First seen · 129 lines · 0 tokens per session scan A d91f09c97855
unreal-engine-cpp is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,296 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-31.
Other cursor rules, from other repositories
08-client-server
IF 判断当前环境是否为客户端 → FabricLoader.getInstance().getEnvironmentType() == EnvType.CLIENT → World.isClient(Yarn 字段;yarn 1.14.4 World.mapping)。不要用 MCP/Forge 的 isRemote.
07-datagen
IF 生成物品/方块模型 JSON → 手动编写 JSON 在 src/main/resources/assets/{modid}/models/.
secure-dev-c
These rules apply to all C source and header files in the repository and aim to prevent memory corruption, code injection, and unsafe system behavior.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
ai-detective-game
Cursor rule "ai-detective-game" from cnwinds/ai-detective, covering ai侦探推理游戏 - 项目核心规则, 项目概述, 技术栈, 项目架构 and 后端服务 (fastapi).
visual-and-observational-rules
Defines the visual aspects of the game and how the player observes the world. This includes map color-coding, screen effects, and the overall simulation style.