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-file-issue/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-file-issue)<a href="https://agentmods.dev/skills/levy-street/world-of-claudecraft/woc-file-issue"><img src="https://agentmods.dev/badge/skills/levy-street/world-of-claudecraft/woc-file-issue/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-file-issue"><img src="https://agentmods.dev/badge/skills/levy-street/world-of-claudecraft/woc-file-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.00347 |
| Opus 5 | $0.00027 | $0.00173 |
| Sonnet 5 | $0.00011 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
woc-file-issue 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 12d 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.
What it actually says
File GitHub Issue
Create a clear, bounded issue in levy-street/world-of-claudecraft.
Confirm authorization
Write to GitHub only when the user explicitly asks to file, create, or open the issue. For draft, rewrite, or proposal requests, return text only. Do not add labels, milestones, projects, or assignees unless requested or unambiguously specified.
Research
- Read the root and relevant local
CLAUDE.mdfiles. - Inspect enough current code or documentation to avoid stale assumptions.
- Search open issues when duplicate risk is meaningful.
- Ask one blocking question only when expected behavior or scope cannot be inferred.
Do not invent reproduction results, environment details, ownership, severity, or implementation decisions.
Write
Use a concise title with the affected area. Structure the body around the problem or opportunity, current and expected behavior, scope, acceptance criteria, relevant implementation context, and verification expectations.
For a bug, include reproduction steps, actual and expected results, and environment only when known. Use unchecked tasks only for independently verifiable acceptance criteria. Put unknown details in HTML comments instead of presenting guesses as facts.
Create with gh issue create only after the authorization condition is satisfied.
Return the final title, issue URL if created, assumptions, and confirmation that no extra
metadata changed unless requested.
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.
- 12d ago First seen · 39 lines · 54 tokens per session scan A a28edd75c70e
woc-file-issue is a skill published in the GitHub repository levy-street/world-of-claudecraft (2,251 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 347 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.