What is wow-addon-development?

A set of instructions for creating and maintaining World of Warcraft add-ons, which are small programs that change the game's interface or behaviour. It covers different WoW versions and their version-specific programming interfaces.

Use it to design, implement, debug, test, port, and package add-ons using Lua, XML, and TOC files, including optional interface mock-ups.

WoW versions do not always provide the same interfaces, so code that works in one client may fail in another. This helps establish the target version and check compatibility before changes are made.

wow-addon-development — Skill for Claude Code by JBurlison

Install

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.

Any agent

npx skills add JBurlison/WoWAddonAPIAgents --skill wow-addon-development

Clone the repo

git clone --depth 1 https://github.com/JBurlison/WoWAddonAPIAgents

Made for: Claude Code.

Or install wow-addon-dev, the plugin that ships this one along with the rest of its 37 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/wow-addon-development/github.svg)](https://agentmods.dev/skills/jburlison/wowaddonapiagents/wow-addon-development)

Your own site

<a href="https://agentmods.dev/skills/jburlison/wowaddonapiagents/wow-addon-development"><img src="https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/wow-addon-development/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jburlison/wowaddonapiagents/wow-addon-development"><img src="https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/wow-addon-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,728 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00081	$0.01728
Opus 5.5	$0.00032	$0.00691
Sonnet 5.5	$0.00016	$0.00346
Haiku 4.5	$0.00008	$0.00173

Measured 2d ago against content hash 0f2445b65eaf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wow-addon-development 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 2d 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.

plugins/wow-addon-dev/skills/wow-addon-development/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

WoW addon development

Establish the target contract

Read wow-client-targets before selecting APIs. Explicit user targets take precedence over existing configuration. Inspect TOCs, packaging configuration, and existing compatibility modules; ask if the target remains ambiguous. Do not silently default to Retail.
Support retail, forever, classic, and all (exactly these three). Classic means the progression branch, not Classic Era. Requests for Era, Anniversary, PTR, beta, or private servers require a scope change, not silent substitution.
Record selected targets, upstream commits, client/interface versions, feature requirements, and unresolved availability in the addon project's documentation. Keep installed plugin files read-only during ordinary addon work.

Keep larger projects anchored to written requirements

For a new addon, a substantial feature, or a long request spanning multiple systems, follow project planning and resumption. Create or update the requirements document and implementation matrix in the user's addon repository, using the packaged templates when no equivalent documents exist. Give requirements stable IDs and connect every requested behavior to implementation work and observable acceptance evidence, including target-specific and visual checks. A small isolated fix can use concise task notes instead.

Work through bounded, dependency-ordered slices. Update the matrix and its checkpoint after each slice and before a handoff or context reset. On resumption, read those files and inspect the recorded revision before continuing; reconcile new user instructions without silently losing earlier requirements. Existing authorization remains valid: the documents organize work and do not create an extra approval gate. Keep unresolved required behavior visible instead of marking the whole project complete because the current slice passes.

Ask about a UI mock-up before implementation

Read the full file on GitHub · 60 lines

Files

What ships with it

9 files 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.

Changes

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.

2d ago Changed · +6 lines · +1 tokens per session 0f2445b65eaf
4d ago Changed · +6 lines · +8 tokens per session a94d32772659
6d ago Changed · +8 lines · +7 tokens per session 03edef457284
7d ago First seen · 40 lines · 65 tokens per session scan A e2947b7b87fe

Subscribe to this mod's changes

wow-addon-development is a skill published in the GitHub repository JBurlison/WoWAddonAPIAgents (73 stars, last pushed 3d ago), licensed MIT. It adds 81 tokens to every session and 1,728 once invoked, about $0.0003 per session on Opus 5.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-11-01.

Game development

wow-addon-development next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
wow-addon-developmentJBurlison/WoWAddonAPIAgents	Skill	73	3d ago	MIT	A	81	Claude Code
playtest-reportDonchitos/Claude-Code-Game-Studios	Skill	37k	20d ago	MIT	A	20	Claude Code
godot-signals-groupsgamedev-skills/awesome-gamedev-agent-skills	Skill	7.4k	11d ago	Apache-2.0	A	95	Claude Code
texture-workflowarjun988/blender-skills	Skill	2.0k	2d ago	MIT	A	41	Claude Code
scenario-unreal-gameplayscenario-labs/skills	Skill	3.5k	yesterday	MIT	A	121	Claude Code
motionOpenDCAI/GameFactory-3A	Skill	1.0k	10d ago	Apache-2.0	A	0	Claude Code, Codex
unity-addressablesBesty0728/Unity-Skills	Skill	1.9k	today	MIT	A	25	Claude Code, Codex