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/onlyworlds/toolkit/parsingnpx skills add OnlyWorlds/toolkit --skill parsinggit clone --depth 1 https://github.com/OnlyWorlds/toolkitWhat 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.00078 | $0.03927 |
| Opus 5 | $0.00039 | $0.01963 |
| Sonnet 5 | $0.00016 | $0.00785 |
| Haiku 4.5 | $0.00008 | $0.00393 |
Grade A, and why
onlyworlds-parsing 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OnlyWorlds Parsing
Convert worldbuilding text into structured OnlyWorlds JSON.
Quick Reference
| Task | Approach |
|---|---|
| Small text (<2k words) | Single-pass extraction |
| Multiple documents | Document-by-document with running registry |
| Large text (novel, campaign) | Multi-pass: Foundations → Organizations → Dynamics → Sweep |
| Messy notes with contradictions | Parse facts, report conflicts separately |
| User has OW world | Check .ow/ setup first — enables reconciliation |
| User has no account | Parse to standalone JSON — works great |
| Second parse of same world | Revise earlier elements with new discoveries |
| Ongoing project with existing world | Extract-first, then reconcile (Step 4b) — outputs CREATE/ENRICH/SKIP |
| Enrich links on existing elements | Re-parse with element list in hand, focus on populating link fields |
Key Rules
- Load knowledge first — read schema files before extracting
- World-specific filter — no elements for generic real-world things
- Fields over elements — use Character.physicality, not Trait "Tall"
- Decompose structural splits — one concept often needs multiple types (see below)
- Schema strict — only real OnlyWorlds fields (check schema-reference.md)
- Sparse is valid — a name and type alone make a valid element
- Revise, don't just append — later discoveries transform earlier elements
Instructions
Step 0: Load Knowledge First
Read all four files before extracting — this ensures valid, importable output:
- ../../knowledge/schema-reference.md — field whitelist for all 22 types
- ../../knowledge/element-types.md — the 22 types and when to use each
- ../../knowledge/decision-trees.md — disambiguation for confusing cases
- knowledge/common-errors.md (in this skill's directory) — patterns that cause import failures
Plus, when the user's world lives in Atlas (or you're parsing prose/session notes for an Atlas user): ../../knowledge/atlas-conventions.md — where prose goes (Narrative story), the knowledge system, extension-field rules.
What ships with it
1 file 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 · 340 lines · 78 tokens per session scan A 3be13128a6f0
onlyworlds-parsing is a skill published in the GitHub repository OnlyWorlds/toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 3,927 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-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…