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/orklev2-particlesnpx skills add tweakoz/orkid --skill orklev2-particlesgit 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/orklev2-particles)<a href="https://agentmods.dev/skills/tweakoz/orkid/orklev2-particles"><img src="https://agentmods.dev/badge/skills/tweakoz/orkid/orklev2-particles.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.00083 | $0.02692 |
| Opus 5 | $0.00042 | $0.01346 |
| Sonnet 5 | $0.00017 | $0.00538 |
| Haiku 4.5 | $0.00008 | $0.00269 |
Grade A, and why
orklev2-particles 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orkid Particle System Reference
When answering questions about particles in orkid, consult the files below. All under ork.lev2/.
Key Files
| Component | Header | Implementation |
|---|---|---|
| Particle Core | inc/ork/lev2/gfx/particle/particle.h |
|
| Modular System | inc/ork/lev2/gfx/particle/modular_particles2.h |
src/gfx/particles/modular_particles2.cpp |
| Emitters | inc/ork/lev2/gfx/particle/modular_emitters.h |
src/gfx/particles/modules_emitter_*.cpp |
| Forces | inc/ork/lev2/gfx/particle/modular_forces.h |
src/gfx/particles/modules_force_*.cpp, modules_attractor_*.cpp |
| Renderers | inc/ork/lev2/gfx/particle/modular_renderers.h |
src/gfx/particles/modules_renderer_*.cpp |
| Materials | (in modular_renderers.h) | src/gfx/particles/renderer_materials.cpp |
| Drawable Integration | inc/ork/lev2/gfx/particle/drawable_data.h |
|
| Pool Module | src/gfx/particles/modules_pool.cpp |
|
| Global Module | src/gfx/particles/modules_global.cpp |
|
| Plug Types | src/gfx/particles/particle_plugs.cpp |
|
| Python Bindings | pyext/src/pyext_gfx_particles.cpp |
|
| Unit Test | unittests/particles.cpp |
|
| Example | examples/python/scenegraph/particles1.py |
Architecture Overview
The particle system is dataflow-graph-based — particles are processed by composable modules connected via typed plugs in a topologically-sorted computation graph.
Signal Flow
GlobalModule (time) ──→ Pool (allocate/age) ──→ Emitter (spawn)
│
──→ Forces (modify velocity)
│
──→ Renderer (draw)
Module Lifecycle
- Data Phase (
ModuleData): created withcreateShared(), plugs defined in_reshapeIOs() - Instance Phase (
ModuleInst):createInstance(GraphInst*)→onLink()→ per-framecompute() - Execution: topological sort ensures dependencies resolve before dependents
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 · 225 lines · 83 tokens per session scan A 11a14cda4164
orklev2-particles is a skill published in the GitHub repository tweakoz/orkid (35 stars, last pushed 23d ago), licensed MIT. It adds 83 tokens to every session and 2,692 once invoked, about $0.0004 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.