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 data-oriented-design-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/data-oriented-design-guide)<a href="https://agentmods.dev/skills/xonovex/platform/data-oriented-design-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/data-oriented-design-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/data-oriented-design-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/data-oriented-design-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.00082 | $0.01096 |
| Opus 5.5 | $0.00033 | $0.00438 |
| Sonnet 5.5 | $0.00016 | $0.00219 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade A, and why
data-oriented-design-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 7d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data-Oriented Design Guidelines
Organize data around access patterns and measure cache traffic before changing performance-critical layouts.
Essentials
- The problem is data movement - Optimize cache traffic, not instruction count, see references/cache-behavior.md
- Design from the data - Model bulk input→output transforms, not idealized objects, see references/data-as-transforms.md
- Measure first - Profile cache misses before changing layout, see references/measurement-and-profiling.md
- Record cheaply, always on - Per-frame accumulating counters recorded via a cached accumulator pointer (one store, no lookup/branch/lock), history allocated only for viewed counters, see references/statistics-recording.md
Layout
- SoA / AoS / AoSoA - Split structs into per-field arrays for hot loops, see references/soa-aos-aosoa.md
- SIMD-friendly layout - Contiguous columns, padding, alignment for vectorization, see references/simd-friendly-layout.md
- Nested / variable-length arrays - Hold child lists in bulk arrays + cache-line chunks, not per-object heap pointers, see references/nested-arrays.md
Processing
- Sequential access - Stream linearly, never chase pointers, see references/access-patterns.md
- Existence-based processing - Bucket by state so branches become loops, see references/existence-based-processing.md
- Batch over one-at-a-time - Transform N items per call, amortize overhead, see references/data-as-transforms.md
- Default to zero - Make all-zero a valid default; reserve 0 for none/neutral, not magic sentinels, see references/zero-as-default.md
What ships with it
15 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.
- eval-queries.json 5.4 KB
- evals.json 3.7 KB
- moon.yml 166 B
- references/access-patterns.md 2.6 KB
- references/cache-behavior.md 3.1 KB
- references/data-as-transforms.md 2.7 KB
- references/existence-based-processing.md 2.7 KB
- references/handles-and-indices.md 3.2 KB
- references/measurement-and-profiling.md 3.0 KB
- references/nested-arrays.md 2.9 KB
- references/simd-friendly-layout.md 2.9 KB
- references/soa-aos-aosoa.md 3.1 KB
- references/statistics-recording.md 2.6 KB
- references/zero-as-default.md 1.6 KB
- SOURCES.md 4.0 KB
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.
- 7d ago Changed · +2 lines eef4b9c1f13e
- 1mo ago First seen · 53 lines · 82 tokens per session scan A ce40fcce6527
data-oriented-design-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 1,096 once invoked, about $0.0003 per session on Opus 5.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.
docker
Use when authoring or auditing a Dockerfile, shrinking a bloated image, hardening a container that runs as root, picking a base image, or wiring a Compose dev loop with hot reload. NOT CI builds or deploy-to-host (that is deployment), NOT k8s autoscaling (that is scaling), NOT app-level injection or secrets-in-code…
kastell
Server security auditing, hardening, and fleet management. 457 security checks across 30 categories (SSH, Firewall, Docker, TLS, HTTP Headers), CIS/PCI-DSS/HIPAA compliance mapping, 24-step production hardening, and 13 MCP tools. Supports Hetzner, DigitalOcean, Vultr, and Linode with Coolify, Dokploy, and bare VPS…
ilo
Run builds, tests, and other tooling inside a reproducible, containerized dev environment via the ilo CLI instead of on the host. Use this whenever a project relies on ilo, devcontainers, or container-based build environments — it has a .ilo.rc / .ilo/ilo.rc, dev/ argument files, a Containerfile/Dockerfile, a…
docker-compose-local-setup
Creates or updates local multi-service orchestration using docker compose. Covers compose.yaml design, service health checks, dependson readiness, env files, named volumes, migrations/seeds jobs, verification commands, and cleanup workflows for local development.
compose
A guide to Docker Compose, a tool for defining and running applications made of multiple containers, such as a web app, API, and database.