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 skills/tweakoz/orkid/orkcore-subsystemnpx skills add tweakoz/orkid --skill orkcore-subsystemgit clone --depth 1 https://github.com/tweakoz/orkidWrote 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/tweakoz/orkid/orkcore-subsystem)<a href="https://agentmods.dev/skills/tweakoz/orkid/orkcore-subsystem"><img src="https://agentmods.dev/badge/skills/tweakoz/orkid/orkcore-subsystem.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.00053 | $0.00995 |
| Opus 5 | $0.00026 | $0.00498 |
| Sonnet 5 | $0.00011 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
orkcore-subsystem 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orkid Subsystem Framework Reference
When answering questions about subsystem management in orkid, consult these files.
Key Files
| Component | Location |
|---|---|
| Subsystem Base | ork.core/inc/ork/application/subsystem.h |
| Subsystem Impl | ork.core/src/application/subsystem.cpp |
| OPQ Subsystem | ork.core/inc/ork/application/subsystem_opq.h |
| Core Subsystem | ork.core/inc/ork/application/subsystem_core.h |
| Catalog Subsystem | ork.core/inc/ork/application/subsystem_catalog.h |
| GPU Subsystem | ork.lev2/inc/ork/lev2/subsystem_gpu.h |
| Audio Subsystem | ork.lev2/inc/ork/lev2/subsystem_audio.h |
| Lev2 Subsystem | ork.lev2/inc/ork/lev2/subsystem_lev2.h |
| Application (registry) | ork.core/inc/ork/application/application.h |
| Python Bindings | ork.core/pyext/pyext_application.cpp |
| Tests | ork.core/pyext/tests/test_subsystem.py |
| Ordering Tests | ork.core/tests/test_subsystem_ordering.py |
Architecture Overview
Subsystem Lifecycle (FSM-Based)
UNINITIALIZED → INITIALIZING → READY
↓ (error)
ERROR
READY → SHUTTING_DOWN → TERMINATED
Each state is an FSM LambdaState — subsystem factories override _onenter callbacks.
Factory Functions
createOpqSubsystem() — OPQ task queue lifecycle
createCoreSubsystem() — Core orkid runtime (depends on OPQ)
createCatalogSubsystem() — Asset catalog (depends on OPQ)
createGpuSubsystem() — GPU context (depends on CORE)
createAudioSubsystem() — Audio device (depends on GPU)
createLev2Subsystem() — Meta-service: signals when GPU+Audio ready
Dependency Graph
OPQ (no deps)
├── CATALOG (depends on OPQ)
└── CORE (depends on OPQ, optionally CATALOG)
└── GPU (depends on CORE, requires "main" thread)
└── AUDIO (depends on GPU)
└── LEV2 (depends on GPU, optionally AUDIO)
Wave-Based Initialization
- Build waves via topological sort of dependencies
- Each wave: subsystems with all deps satisfied
- Within a wave: respect thread affinity
requires_thread = "main"→ serialize on caller threadrequires_thread = ""→ parallel threads
- Wait for wave completion before next wave
- Circular dependency detection (asserts)
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.
- 3d ago First seen · 115 lines · 53 tokens per session scan A f9deca43c298
orkcore-subsystem is a skill published in the GitHub repository tweakoz/orkid (35 stars, last pushed 23d ago), licensed MIT. It adds 53 tokens to every session and 995 once invoked, about $0.0003 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-01.
Other skills, from other repositories
luban-dev
Luban 游戏配置全栈工具,支持枚举/Bean/数据表的增删改查、代码生成、TEngine 集成。触发场景:(1) 编辑游戏配置数据(配置表/数据表/道具表/技能表/奖励表/活动表),(2) 新增/修改/删除配置表结构,(3) 定义枚举/Bean/字段,(4) 导表/生成配置代码,(5) 编写 luban.conf 或 Schema 定义,(6) Luban 类型系统/校验器问题。即使用户未明确说"Luban",只要是编辑游戏配置数据,也应使用此技能。.
html-to-ugui
HTML 原型转 Unity UGUI 智能 Prefab 生成管线。通过 AI 生成符合 UI-DSL 的 HTML,用 Playwright/浏览器烘焙 JSON v2 坐标、图片和适配意图,再导入 Unity 由 HtmlToUGUIBaker 生成可维护、多终端适配的 UGUI Prefab。触发场景:(1) 需要从自然语言生成 Unity UGUI 界面 (2) 需要从 HTML 原型烘焙 UGUI (3) UI 中包含图片并希望一键导入/绑定 Sprite (4) 需要 PC/mobile/pad 多终端适配 Prefab。.
metasounds
Create and modify MetaSound Source assets — add/connect nodes, wire pins, set input defaults, and play procedurally (MetaSoundService). Use when the user asks to create a MetaSound, build or edit a MetaSound graph, add operator/input/output nodes, or generate procedural audio.
dart-model-upgrade
DART Model Upgrade: audit and update DART AI infrastructure for model or coding-agent upgrades, including named models, reasoning modes, migrations, compatibility reviews, and visual simulation-debugging evaluations.
dart-verify-sim
DART Verify Sim: text-first and visual checks for 3D scenes and physics (metrics, scene dump, trajectories, headless render, image verdict/golden).
dart-architecture
DART Architecture: the DART 7 multi-physics, multi-solver, multi-backend simulation pipeline and where each abstraction is owned.