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/project-setupnpx skills add OnlyWorlds/toolkit --skill project-setupgit 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.00068 | $0.01324 |
| Opus 5 | $0.00034 | $0.00662 |
| Sonnet 5 | $0.00014 | $0.00265 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
onlyworlds-project-setup 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OnlyWorlds Project Setup
Connect your project to your OnlyWorlds world.
CRITICAL: Confirm Location Before Creating Files
This skill writes files to disk (.env, .ow/, .gitignore). Show the user where setup will happen and get explicit confirmation before creating anything.
What Gets Created
project/
├── .env # API credentials (gitignored)
├── .ow/ # OnlyWorlds project data (gitignored)
│ ├── config.json # World info and settings
│ ├── world-cache.json # Cached elements (name, uuid, type)
│ └── last-parse.md # Last parse status
└── .gitignore # Updated to ignore .env and .ow/
Instructions
Step 1: Confirm Location
pwd
Show user: "Setting up OnlyWorlds project in: {pwd}. This creates .ow/ folder, .env file, and updates .gitignore. Is this the right place?"
Wait for explicit "yes" before proceeding. If they want a different location, they specify or cd there first.
Step 2: Check Existing Setup
Look for .ow/ in current directory.
- Exists: "Project already connected to '{world_name}'. Refresh cache / Add world / Continue?"
- Not exists: Proceed with new setup.
Step 3: Get Credentials
Ask for API-Key (from world settings) and API-Pin (the world's PIN). If user doesn't have these, direct them to onlyworlds.com.
The API-Key may be a prefixed key — ow_w_… (world-write) or ow_r_… (read-share) — or a legacy 10-digit key (still valid forever, no longer issued). Any of these works here; store it as-is. The API-Pin is required for writes, and for reads if the world is walled.
Then ask credential storage preference:
| Mode | Stored in .env | Behavior |
|---|---|---|
| full (default) | API-Key + API-Pin | Fully automated |
| key-only | API-Key only | PIN asked for write ops |
| manual | Nothing | Both asked each session |
Step 4: Validate Credentials + Fetch World Info
curl -s "https://www.onlyworlds.com/api/v2/world" \
-H "API-Key: {api_key}" \
-H "API-Pin: {api_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 · 156 lines · 68 tokens per session scan A af6d32474bea
onlyworlds-project-setup is a skill published in the GitHub repository OnlyWorlds/toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,324 once invoked, about $0.0003 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…