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 skills add xonovex/platform --skill ecs-guidegit clone --depth 1 https://github.com/xonovex/platformWrote 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/skills/xonovex/platform/ecs-guide)<a href="https://agentmods.dev/skills/xonovex/platform/ecs-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/ecs-guide/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/skills/xonovex/platform/ecs-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/ecs-guide.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.00088 | $0.01001 |
| Opus 5 | $0.00044 | $0.00500 |
| Sonnet 5 | $0.00018 | $0.00200 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
ecs-guide 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 today.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entity-Component-System Guidelines (Data-Oriented)
Architecture for a data-oriented ECS: how entities and components are stored, how systems iterate them, and how to bridge the ECS to stateful external systems (renderer, physics) without losing parallelism or cache locality. For the underlying cache/layout reasoning see data-oriented-design-guide; for the renderer the ECS feeds, see gpu-rendering-guide; for the allocators behind component storage see memory-management-guide.
Requirements
- A component is plain data (POD-ish struct); behavior lives in systems, not components.
- Storage groups entities by their set of components, so a system can walk matching components linearly.
Essentials
- Entity type = component bitmask - Group entities of identical component sets contiguously; iterate by type, see references/storage-and-archetypes.md
- One component instance per type - Model "many of a thing" with child entities or a list-component, not duplicate components, see references/single-vs-multiple-components.md
- Systems are filter-and-batch loops - Select types matching a bitmask, walk co-located arrays in a tight loop, go wide across cores, see references/systems-and-iteration.md
- Default to brute-force sync - Re-push matching entities each frame; add dirty flags / change lists only when profiling proves it, see references/change-tracking-and-sync.md
- Never propagate via callbacks - Observer callbacks bypass declared read/write deps and break the parallel scheduler; reserve them for lifecycle, see references/change-tracking-and-sync.md
- Feed renderers through interfaces + visibility bitmasks - Components expose render/shader interfaces; cull once per viewer into a bitmask, see references/rendering-integration.md
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 51 lines · 88 tokens per session scan A a8d833179f30
ecs-guide is a skill published in the GitHub repository xonovex/platform (5 stars, last pushed 2d ago), licensed MIT. It adds 88 tokens to every session and 1,001 once invoked, about $0.0004 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-09-08.
Other skills, from other repositories
harbor-daytona
Use Harbor's Daytona sandbox platform for computer use — creating sandboxes, taking screenshots, sending mouse/keyboard input, and building agent loops. Use when the user wants to interact with a GUI, automate a desktop, do computer use, control a browser visually, or run Claude computer use against a Daytona sandbox.
gamedev-multiplayer
Use when adding multiplayer or netcode to a game — client-server vs P2P, server authority and anti-cheat, state replication vs RPCs, prediction and reconciliation, lag compensation, plus Godot 4 / Unity NGO / Unreal wiring. NOT single-player gameplay (that is godot, unity, unreal), NOT matchmaking or server hosting…
gamedev-pathing
Use when making NPCs, enemies, or units navigate a level — grid vs waypoint vs navmesh, A/JPS, navmesh baking and agent radius, off-mesh links, steering, RVO crowd avoidance, and flow fields in Godot 4.x, Unity, Unreal. NOT collision response or character controllers (that is gamedev-physics), NOT aggro or difficulty…
gamedev-physics
Use when working with a game engine's physics — rigid bodies, colliders, collision layers and masks, character controllers, joints, forces versus impulses, raycasts and shapecasts, or when a simulation is unstable (tunnelling, jitter, missed overlaps). Covers the Godot, Unity and Unreal equivalents. NOT rendering or…
hz-xr-simulator-setup
Sets up the Meta XR Simulator for testing Meta Quest and Horizon OS apps without a physical device. Use when configuring device-free testing for Unity or Unreal projects.
game-reply-options
Offer 2-5 context-specific clickable reply buttons in the JHT game chat when they genuinely make the user's next decision easier. Use only for a small bounded choice; otherwise answer normally with jht-send. Never use these as a fixed onboarding tree.