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/surveynpx skills add OnlyWorlds/toolkit --skill surveygit 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.00089 | $0.01580 |
| Opus 5 | $0.00044 | $0.00790 |
| Sonnet 5 | $0.00018 | $0.00316 |
| Haiku 4.5 | $0.00009 | $0.00158 |
Grade A, and why
survey scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://www.onlyworlds.com/api/v2/world" \ How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Survey
Read an entire world -- from a folder on disk or via the API -- and produce a creative brief: not a data dump, but a reading of the world's soul.
Quick Reference
| Step | Action |
|---|---|
| 0 | Pick the source: world FOLDER (path; no credentials) or API (credentials) |
| 1 | Folder: read world.json + walk elements/*/ (see knowledge/world-folder.md). API: get credentials |
| 2 | Validate source + world info |
| 3 | Load all element types (folder read or parallel API fetch) |
| 4 | Read, connect, synthesize |
| 5 | Write the brief |
Folder source: if the user has an Atlas world folder, converter output, or any OW-shaped folder, read it directly -- world.json for meta, every .json under elements//, keyed on internal id (never the filename). Steps 4-5 are identical from there. No account, no network.
| World Size | Brief Length | Approach |
|---|---|---|
| Under 20 elements | Short (~60-80 lines) | Go deep on each element |
| 20-100 elements | Standard (~100-150 lines) | Cover shape and highlights |
| 100-300 elements | Full (~150-200 lines) | Find clusters and themes |
| 300+ elements | Focused (~150-200 lines) | Find the skeleton, don't cover everything |
Instructions
Step 1: Pick the Source
- World folder (no credentials): the user has an Atlas world folder or any OW-shaped folder. Read
world.jsonfor meta, walkelements/*/keying on internalid(knowledge/world-folder.md) — then skip to Step 4. - API: check for
.ow/config.jsonin current directory first:
| Config Found | credential_mode | Action |
|---|---|---|
| Yes | full | Load API-Key + API-Pin from .env |
| Yes | key-only | Load API-Key from .env, ask user for PIN |
| Yes | manual | Ask user for both |
| No | — | Check .env for ONLYWORLDS_API_KEY / ONLYWORLDS_API_PIN, then ask user |
Step 2: Validate + Fetch World
curl -s "https://www.onlyworlds.com/api/v2/world" \
-H "API-Key: {key}" -H "API-Pin: {pin}"
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 · 130 lines · 89 tokens per session scan A c1affb9b925b
survey is a skill published in the GitHub repository OnlyWorlds/toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,580 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…