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/councilnpx skills add OnlyWorlds/toolkit --skill councilgit 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.00069 | $0.01850 |
| Opus 5 | $0.00034 | $0.00925 |
| Sonnet 5 | $0.00014 | $0.00370 |
| Haiku 4.5 | $0.00007 | $0.00185 |
Grade C, and why
onlyworlds-council scanned grade C with 2 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 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
### Step 4: Gather Credentials 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/worldapi/council/browse/" How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OnlyWorlds Council
Browse, discuss, and participate in schema governance.
Quick Reference
| User Says | Action |
|---|---|
| "Does anyone else have this problem?" | Browse motions by element type |
| "The schema needs a death_date field" | Draft an amendment |
| "This already works with Construct" | Draft a precedent |
| "I want to propose a change" | Draft a motion |
| "What motions exist for Character?" | Browse by element type |
| "Submit my motion" | Submit via proxy endpoint |
| Item Type | Purpose |
|---|---|
| Motion | A schema limitation or question |
| Precedent | "The schema already handles this" |
| Amendment | "The schema needs to change" |
What Is Council?
The OnlyWorlds Council is where worldbuilders propose and discuss schema changes. Characters from across all worlds serve as delegates — committed representatives who submit motions on behalf of their world.
Council data lives at council.onlyworlds.com. The toolkit browses via a public proxy and submits via an authenticated one.
Prerequisites for Submitting
Browsing is free. Submitting requires:
- An OnlyWorlds world with an API key and PIN -- submission accepts either the legacy 10-digit numeric key or a prefixed write key (
ow_w_...). A bare read key (ow_r_...) is rejected -- submission needs write scope - A delegate — a Character from the user's world that has been committed as a council delegate at
council.onlyworlds.com(costs 1000 tokens, one-time) - Tokens — each submission stakes 100-1000 tokens, deducted from the user's daily quota
If the user hasn't committed a delegate yet, direct them to council.onlyworlds.com → log in → Quarters → Commit a Character. They cannot submit via the toolkit until a delegate exists.
Instructions
Step 1: Browse Existing Motions
Before drafting anything, check what already exists.
curl -s "https://www.onlyworlds.com/api/worldapi/council/browse/"
Response JSON contains:
motions[]— each withid,name,description(human text, metadata stripped),supertype(Motion/Precedent/Amendment),subtype(element type),meta(author, votes, status, parent, etc.),created_atdelegates[]— each withid,name,image_urltotal_motions,total_delegates
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 · 204 lines · 69 tokens per session scan C 323122f50b37
onlyworlds-council is a skill published in the GitHub repository OnlyWorlds/toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 1,850 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (harvests environment variables, 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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.