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-filesystemnpx skills add tweakoz/orkid --skill orkcore-filesystemgit 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-filesystem)<a href="https://agentmods.dev/skills/tweakoz/orkid/orkcore-filesystem"><img src="https://agentmods.dev/badge/skills/tweakoz/orkid/orkcore-filesystem.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.1 | $0.00057 | $0.00984 |
| Opus 5 | $0.00028 | $0.00492 |
| Sonnet 5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
orkcore-filesystem 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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orkid Core Filesystem Reference
When answering questions about file I/O, paths, or virtual filesystem in orkid, consult the files below.
Key Files
| Component | Header | Implementation |
|---|---|---|
| Path | ork.core/inc/ork/file/path.h |
ork.core/src/file/Path.cpp |
| FileEnv (singleton) | ork.core/inc/ork/file/fileenv.h |
ork.core/src/file/fileenv.cpp |
| FileDev (abstract) | ork.core/inc/ork/file/filedev.h |
ork.core/src/file/filedev.cpp |
| FileDevContext | ork.core/inc/ork/file/filedevcontext.h |
|
| FileDevStd | ork.core/inc/ork/file/filestd.h |
ork.core/src/file/filestd.cpp |
| FileDevRam | ork.core/inc/ork/file/filedevram.h |
ork.core/src/file/filedevram.cpp |
| File (high-level) | ork.core/inc/ork/file/file.h |
ork.core/src/file/file.cpp |
| DataBlock | ork.core/inc/ork/kernel/datablock.h |
|
| ChunkFile | ork.core/inc/ork/file/chunkfile.h |
ork.core/src/file/chunkfile.cpp |
Architecture Overview
Path Abstraction (ork::file::Path)
- Unified path supporting native, POSIX, URL, and asset catalog forms
- Path composition:
operator/(),operator+() - Decomposition: protocol, folder, file, extension
- Asset catalog paths:
namespace|assetid(detected via|character) - Filesystem queries:
doesPathExist(),isFile(),isFolder()
Path Expansion (thread-safe)
file::setPathExpander("assetcache", stage_dir / "assetcache");
// Then: "<assetcache>/foo" expands to "/path/to/stage/assetcache/foo"
// Also: "assetcache://foo" works via URI protocol
Expansion order:
~->$HOMEkey://rest-> registered path +/rest<key>-> registered path${ENV_VAR}-> environment variable value
Registered Expanders (from application.cpp)
<staging>/<stage>-> staging directory<assetcache>-><stage>/assetcache<temp>-> temp directory<ork_data>-> orkid data directory- URI protocols:
src://,data://,ork_core://,ork_lev2://
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.
- 4d ago First seen · 85 lines · 57 tokens per session scan A f95c29466936
orkcore-filesystem is a skill published in the GitHub repository tweakoz/orkid (35 stars, last pushed 24d ago), licensed MIT. It adds 57 tokens to every session and 984 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-elf-malware
Analyze malicious Linux ELF binaries — botnets, cryptominers, ransomware, and rootkits targeting Linux servers, containers, and cloud infrastructure — through static analysis, dynamic tracing, and reverse engineering of x8664 and ARM samples. Use when investigating Linux malware, triaging a suspicious ELF binary…
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.