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-applicationnpx skills add tweakoz/orkid --skill orkcore-applicationgit 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-application)<a href="https://agentmods.dev/skills/tweakoz/orkid/orkcore-application"><img src="https://agentmods.dev/badge/skills/tweakoz/orkid/orkcore-application.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.00056 | $0.00995 |
| Opus 5 | $0.00028 | $0.00498 |
| Sonnet 5 | $0.00011 | $0.00199 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
orkcore-application 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orkid Application Framework Reference
When answering questions about application structure in orkid, consult these files.
Key Files
| Component | Location |
|---|---|
| Application (C++) | ork.core/inc/ork/application/application.h |
| Application Impl | ork.core/src/application/application.cpp |
| Python Bindings | ork.core/pyext/pyext_application.cpp |
| ComponentizedApplication | obt.project/scripts/ork/app/application.py |
| Logger UI Component | obt.project/scripts/ork/app/loggerui.py |
| Frame Profiler | obt.project/scripts/ork/app/frame_profiler.py |
Architecture Overview
AppInitData
Singleton struct (appinitdata()) centralizing initialization config:
- Command-line parsing (Boost.ProgramOptions)
- Window config: width, height, fullscreen, MSAA/SSAA
- Audio config: device names, channels, framesize, stream sync
- Target UPS/FPS rates
- Pre/post init operation queues
Path Expanders (set during init)
<assetcache> → <stage>/assetcache
<staging> → staging directory root
<ork_data> → orkid data directory
<ork_ecsscenes> → ork.data/ecsscenes
<ork_envmaps> → staging/envmaps
<ork_testdata> → ork.data/tests
URI Contexts
src:// → ork.data/src
data:// → ork.data
lev2:// → ork.data/platform_lev2
orkid:// → orkid root
ork_core://→ ork.core source
ork_lev2://→ ork.lev2 source
Environment Variables
ORKID_ASSET_MANIFEST_DIRS— colon-separated manifest pathsORKID_AUDIO_INPUT_DEVICE/ORKID_AUDIO_OUTPUT_DEVICEORKID_AUDIO_FRAMESIZE— buffer size (default 1024)ORKID_AUDIO_STREAM_SYNC— audio/graphics syncORKID_DISABLE_ALWAYS_ON_TOP— window flagORKID_LOGGER_BACKEND— logger selection
ComponentizedApplication (Python)
High-level Python app framework with ECS-like component pattern:
class MyApp(ComponentizedApplication):
def __init__(self):
super().__init__()
self.logger = self.addComponent("logger", loggerui.LoggerUIComponent, ...)
self.createEzApp(width=1280, height=720)
def _onUiInit(self):
lg = self.ezapp.topLayoutGroup
# Build UI here
def _onGpuInit(self, ctx):
# GPU resources here
def _onUpdate(self, updinfo):
# Per-frame logic here
app = MyApp()
app.ezapp.mainThreadLoop()
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 · 113 lines · 56 tokens per session scan A bc6851a0ea5f
orkcore-application is a skill published in the GitHub repository tweakoz/orkid (35 stars, last pushed 22d ago), licensed MIT. It adds 56 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
host-pattern
Use when adding a new domain to Nuclear's plugin system, or implementing a host. Covers the host pattern (how player functionality is exposed to plugins), the host interface and API class structure, how hosts are implemented in the player, error handling conventions, and what files to create and modify. Trigger…
creating-components
Use when creating new UI components in packages/ui. Covers component structure, tests, stories, and what to avoid.
writing-docs
Use when writing or editing documentation in packages/docs. Covers Gitbook markdown syntax, special blocks, page structure, and the SUMMARY.md table of contents. Trigger phrases include "write docs", "add documentation", "docs page", "gitbook", "user manual".
writing-plugins
Use when writing, scaffolding, or modifying Nuclear plugins. Covers plugin structure, manifest, entry point, provider types, available APIs, and publishing. Trigger phrases include "create a plugin", "write a plugin", "plugin scaffold", "streaming provider", "metadata provider".
commands-create-slash-command
Create or update Agent Zero slash commands for the built-in Commands plugin. Use when the user asks to add, edit, duplicate, or refine a reusable /command backed by YAML config plus text/python content files.
python
Hermetic Python runtime (uv-managed CPython) for native Python plugins.