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/ouzlifaneyassine1-dot/onyx-engineWrote 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/commands/ouzlifaneyassine1-dot/onyx-engine/gameskill)<a href="https://agentmods.dev/commands/ouzlifaneyassine1-dot/onyx-engine/gameskill"><img src="https://agentmods.dev/badge/commands/ouzlifaneyassine1-dot/onyx-engine/gameskill/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/commands/ouzlifaneyassine1-dot/onyx-engine/gameskill"><img src="https://agentmods.dev/badge/commands/ouzlifaneyassine1-dot/onyx-engine/gameskill.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.02130 |
| Opus 5 | $0.00000 | $0.01065 |
| Sonnet 5 | $0.00000 | $0.00426 |
| Haiku 4.5 | $0.00000 | $0.00213 |
Grade A, and why
gameskill 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 8d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are capturing what we just learned in this game-development session into Onyx Engine's skill library, so the next agent (and every onyx user) gets to start where we ended.
This is the meta-skill: the loop that turns ad-hoc fixes into durable, reusable expertise.
What "Onyx Engine" is, so you're grounded
Three repos, one ecosystem:
~/development/OnyxEngine— the desktop engine (Godot fork in C++) + the canonical CLI. The engine source lives ateditor/,core/, and the Summer-specific module atmodules/1onyx_engine/. The onyx CLI lives attools/onyx-cli/. It ships asnpm i -g onyx-engine. It does install/login/create/run for the engine, plusonyx skills install --as-claude-skillwhich writes a curated subset of skills into~/.claude/skills/for any agent to auto-discover.~/development/PublicOnyxEngine— the web app at OnyxEngine.com. Has its own AI skill stores atsrc/lib/ai/skills/bundled/andpublic/knowledge/onyx/skills/for the in-browser chat agent. ALSO has its own MCP-style consumers of the engine API (src/lib/bridge/direct-executor.ts,src/lib/ai/tools/run-and-verify.ts) which call the same engine endpoints the CLI does.- The active game project — usually
~/development/<game-name>(Godot 4.6) or whatever game we were just working on. Real working code in this repo is the gold standard for examples.
The skill system is the value flywheel: every game we ship teaches lessons → the lessons become skills → the next user (or AI) starts smarter. Your job here is to close that loop for what we just did.
Cross-repo change awareness — read this before any non-trivial fix
When the lesson is "the engine should expose more / behave differently," the change usually crosses repo boundaries. Map the layers before you edit:
[active game] → calls MCP / web app
↓
[onyx-cli MCP server (TypeScript)] → calls /api/ops + /api/state/* on the engine
↓
[Onyx Engine binary (C++ in OnyxEngine repo)] — source of truth for what the API can return
[PublicOnyxEngine web app (TypeScript)] → also calls the same engine endpoints via direct-executor or Redis bridge
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.
- 8d ago First seen · 104 lines · 0 tokens per session scan A 5580c233a900
gameskill is a command published in the GitHub repository ouzlifaneyassine1-dot/onyx-engine (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,130 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 commands, from other repositories
memory-budget
Define or review memory budgets, ownership, and key memory risks.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.