World of ClaudeCraft is a browser-based classic-style multiplayer online game with a persistent shared world that can also run locally or be controlled through a Python reinforcement-learning interface. Players can quest and raid in the online world, while developers can host it themselves and train AI agents to play. The catalogue skills, agents, instructions, hooks, and setting support workflows for interacting with and developing the game.
Borrowing it
Nothing to install: this file belongs to levy-street/world-of-claudecraft. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/levy-street/world-of-claudecraft/main/.agents/skills/woc-extract-and-test/SKILL.mdgit clone --depth 1 https://github.com/levy-street/world-of-claudecraftWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/levy-street/world-of-claudecraft/woc-extract-and-test)<a href="https://agentmods.dev/skills/levy-street/world-of-claudecraft/woc-extract-and-test"><img src="https://agentmods.dev/badge/skills/levy-street/world-of-claudecraft/woc-extract-and-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/levy-street/world-of-claudecraft/woc-extract-and-test"><img src="https://agentmods.dev/badge/skills/levy-street/world-of-claudecraft/woc-extract-and-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 56 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
What 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.1 | $0.00055 | $0.00564 |
| Opus 5 | $0.00028 | $0.00282 |
| Sonnet 5 | $0.00011 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
woc-extract-and-test 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 13d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract and Test
Implement the requested behavior with the smallest clean module boundary and direct regression coverage.
Load context
- Read the root
CLAUDE.mdin full. - Read the relevant local
CLAUDE.mdbefore opening or editing that area. - Run
git status --shortand preserve unrelated work. - Inspect the production path, its callers, and nearby tests before choosing a seam.
Apply canonical architecture rules to the concrete change without copying them here.
Before implementing database-backed behavior, invoke woc_database_performance for a
read-only checkpoint when the change can affect SQL or query call sites, schema or indexes,
query frequency or cardinality, pool configuration, lock scope, timeout policy, or stored-data
growth, including database driver/dependency upgrades and PostgreSQL
engine/resource/configuration/topology changes. Carry its concrete bounds and evidence
requirements into the test-first contract.
Choose the workflow
For a bug fix:
- Reproduce the defect through the real production path.
- Add a focused test that fails for the intended reason.
- Confirm the test is red before changing production code.
- Make the smallest coherent fix.
- Add nearby edge cases only when they protect the same contract.
For a feature or refactor:
- Identify the existing module, coordinator, state owner, or extension seam.
- Place behavior in a pure sibling module, current state owner, or thin adapter.
- Separate pure decisions from I/O, rendering, global state, and transport.
- Give the extracted unit direct tests and keep consumers thin.
- When relocating behavior, preserve semantics before redesigning anything.
Do not grow a monolith when a tested sibling is appropriate, introduce a framework for one call site, bypass existing seams to reach private state, or build parallel versions of the same rule. Preserve determinism, parity, localization, and persistence contracts. Do not commit unless explicitly asked.
Validate
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.
- 13d ago First seen · 64 lines · 55 tokens per session scan A c7a4c1b340e1
woc-extract-and-test is a skill published in the GitHub repository levy-street/world-of-claudecraft (2,251 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 564 once invoked, about $0.0003 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-30.
Other skills, from other repositories
team-combat
A coordinated workflow for designing, building, and testing a game's combat features with specialists in gameplay, enemy AI, visual effects, sound, and quality assurance.
unity-tdd
This skill should be used when the user asks to write tests first, do TDD, implement a feature or bugfix using test-driven development, add unit tests before coding, write EditMode or PlayMode tests, or set up Unity Test Runner. Also applies when a user says 'red green refactor', 'write a failing test', or…
unity-testing
Unity 6 testing guide. Use when writing unit tests, integration tests, or doing TDD with Unity Test Framework. Covers Edit Mode and Play Mode tests, NUnit attributes ([Test], [UnityTest], [SetUp], [TearDown]), testing MonoBehaviours and coroutines, and CI/CD integration. Based on Unity 6.3 LTS documentation.
unity-testrunner
Unity Test Framework CLI automation and test writing patterns. Masters batchmode execution, NUnit assertions, EditMode/PlayMode testing, and TDD workflows. Use PROACTIVELY for test automation, CI/CD pipelines, or test-driven development in Unity.
roblox-tdd
Use to drive Roblox / Luau implementation via red-green-refactor cycles with TestEZ or Jest-Roblox. Use when the user says "TDD", "test-driven", "write the test first", "test it properly", before implementing any non-trivial Luau module, or any time disciplined coverage is needed before code lands.
roblox-scrum-dev-story
Executes Roblox story implementation following a context-filled story spec file, using TDD, StyLua, Rojo, and the Roblox Studio MCP integration. Use when the user says "develop story [key]" or "implement the next story".