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/rhtevan/agentfs/okf-bundle-setupnpx skills add rhtevan/agentfs --skill okf-bundle-setupgit clone --depth 1 https://github.com/rhtevan/agentfsWhat 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.00019 | $0.05155 |
| Opus 5 | $0.00010 | $0.02577 |
| Sonnet 5 | $0.00004 | $0.01031 |
| Haiku 4.5 | $0.00002 | $0.00515 |
Grade A, and why
okf-bundle-setup 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 — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OKF Bundle Setup
Scope guard: This skill is not available in LITE scope projects. LITE scope does not support skills or knowledge bundles. If the target project's AGENTS.md contains
agentfs-scope: lite, refuse with a clear message.
Create, organize, or update a directory as an Open Knowledge Format (OKF) v0.1 knowledge bundle.
For the full OKF specification, see references/okf-spec-summary.md.
Prerequisites
- bash available (for scaffolding / scanning scripts)
- Write access to the target directory
Inputs
The skill accepts an optional bundle path argument:
| Input | Example | Behaviour |
|---|---|---|
| (none) | "set up an okf bundle" |
Use ~/.agents/knowledge/ as the bundle root |
| Explicit path | "create an okf bundle at docs/data-catalog" |
Use the given path as the bundle root |
Procedure
Execute these phases in order. Each phase references a helper script or gives inline agent instructions.
Naming Convention — lowercase kebab-case
All bundle and sub-bundle directory names MUST follow
lowercase kebab-case (this-style):
- Only lowercase letters (
a-z), digits (0-9), and hyphens (-) - No underscores, spaces, uppercase, or special characters
- Maximum 25 characters
- Must not start or end with a hyphen
Examples:
- ✅
rca-labeled-dataset,sales-data,ml-training-configs - ❌
rca_labeled_dataset(underscores),RCA-Data(uppercase),my data(spaces)
When the input directory name violates this convention, the agent
must rename it to conform (e.g., rca_labeled_dataset →
rca-labeled-dataset). The normalization rule is:
lowercase → replace _ and spaces with - → strip non-alphanumeric
except - → collapse consecutive hyphens → trim leading/trailing
hyphens → truncate to 25 chars.
Reserved directory names (assets, scripts, etc.) are exempt from
the length limit but must still be lowercase kebab-case (they already
are by definition).
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 509 lines · 19 tokens per session scan A 5e3f2d18d273
okf-bundle-setup is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 19 tokens to every session and 5,155 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…