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-dataflownpx skills add tweakoz/orkid --skill orkcore-dataflowgit clone --depth 1 https://github.com/tweakoz/orkidWhat 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.00059 | $0.02162 |
| Opus 5 | $0.00030 | $0.01081 |
| Sonnet 5 | $0.00012 | $0.00432 |
| Haiku 4.5 | $0.00006 | $0.00216 |
Grade A, and why
orkcore-dataflow 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 yesterday.
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orkid Dataflow Graph System Reference
When answering questions about the dataflow system in orkid, consult these files.
Full current architecture: ork.dox/core/dataflow.md (accuracy-passed 2026-08-01, incl. diagrams).
What's new (2026-06/07)
- Composite modules
SubGraphModuleData/LoopModuleData— nested GraphData with promoted boundary plugs, loop carries, index feeds (ork.core/inc/ork/dataflow/subgraph_module.h) CookGraphDriver— family-neutral hook interface the composite runtime delegates nested cook/bake execution to (ork.core/inc/ork/dataflow/cook_driver.h)- Per-node Merkle cook cache — opt-in via
GraphData::_cacheable; modules opt in per class viaDgModuleInst::cookComputeHash/cookStore/cookLoad;GraphInst::computeNodeHashes()+cachedCompute() TypeKeyedVars _implon GraphData AND GraphInst — per-family runtime storage keyed by type, so families (hypermesh/terrain/particles) coexist on one graph- Bypass (
DgModuleData::_bypassed) + select-as-output (GraphData::_output_node) — first-class serialized graph state; bypassed modules splice out viaresolveConnectedOutput() - Python introspection
dflow.plugSpec()/dflow.moduleClasses()— plug schemas and node registry straight from reflection (ork.core/pyext/pyext_dataflow.cpp) - Generic family-neutral modules Min/Max/Lerp/Pow/Vec4Combine (
ork.core/inc/ork/dataflow/basic_modules.h)
Key Files
| Component | Location |
|---|---|
| Main Types | ork.core/inc/ork/dataflow/dataflow.h |
| Module Definitions | ork.core/inc/ork/dataflow/module.h |
| Module Templates | ork.core/inc/ork/dataflow/module.inl |
| Composite Modules (SubGraph/Loop) | ork.core/inc/ork/dataflow/subgraph_module.h |
| Cook Driver Seam | ork.core/inc/ork/dataflow/cook_driver.h |
| Generic Modules (Min/Max/Lerp/Pow/Vec4Combine) | ork.core/inc/ork/dataflow/basic_modules.h |
| Plug Data | ork.core/inc/ork/dataflow/plug_data.h |
| Plug Templates | ork.core/inc/ork/dataflow/plug_data.inl |
| Plug Instances | ork.core/inc/ork/dataflow/plug_inst.h |
| Enums | ork.core/inc/ork/dataflow/enum.h |
| Scheduler | ork.core/inc/ork/dataflow/scheduler.h |
| GraphData Impl | ork.core/src/dataflow/graph_data.cpp |
| GraphInst Impl | ork.core/src/dataflow/graph_inst.cpp |
| Topology Sorter | ork.core/src/dataflow/dataflow_sorter.cpp |
| Register Context | ork.core/src/dataflow/dataflow_context.cpp |
| Python Bindings | ork.core/pyext/pyext_dataflow.cpp |
| Python Test | ork.core/pyext/tests/dataflow.py |
| Particle Modules | ork.lev2/inc/ork/lev2/gfx/particle/modular_particles2.h |
| Particle Emitters | ork.lev2/inc/ork/lev2/gfx/particle/modular_emitters.h |
| Particle Forces | ork.lev2/inc/ork/lev2/gfx/particle/modular_forces.h |
| Particle Renderers | ork.lev2/inc/ork/lev2/gfx/particle/modular_renderers.h |
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.
- yesterday First seen · 176 lines · 59 tokens per session scan A 222f486efc68
orkcore-dataflow is a skill published in the GitHub repository tweakoz/orkid (35 stars, last pushed 21d ago), licensed MIT. It adds 59 tokens to every session and 2,162 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".
analyzing-linux-kernel-rootkits
Detect kernel-level rootkits in Linux memory dumps using Volatility3 linux plugins (checksyscall, lsmod, hiddenmodules), rkhunter system scanning, and /proc vs /sys discrepancy analysis to identify hooked syscalls, hidden kernel modules, and tampered system structures.
triage-issue-local
Repo-specific triage guidance for warp. Only the categories declared overridable by the core triage-issue skill may be specialized here.