WoWAddonAPIAgents: Instructions file for GitHub Copilot

.github/instructions/wow-api-important.instructions.md

WoW client-aware API guidance is an instructions file for GitHub Copilot from JBurlison/WoWAddonAPIAgents. It costs 389 tokens per session, scanned C, original, MIT.

A reference for breaking changes in the World of Warcraft 12.0.0 addon programming interface, including new security rules and removed or deprecated functions.

In plain words
What is it for?
Use it when updating or debugging Lua addons for WoW 12.0.0 and later, especially code handling combat information, instance limits, or protected values.
Why use it?
It prevents developers from relying on older 11.x or earlier API behavior that no longer applies.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is JBurlison/WoWAddonAPIAgents's own configuration. It tells GitHub Copilot how to work on WoWAddonAPIAgents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything WoWAddonAPIAgents configures →

Reuse

Borrowing it

Nothing to install: this file belongs to JBurlison/WoWAddonAPIAgents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/JBurlison/WoWAddonAPIAgents/main/.github/instructions/wow-api-important.instructions.md
Clone the repo
git clone --depth 1 https://github.com/JBurlison/WoWAddonAPIAgents

Made for: GitHub Copilot.

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.

agentmods badge for WoW client-aware API guidance

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jburlison/wowaddonapiagents/wow-api-important/github.svg)](https://agentmods.dev/instructions/jburlison/wowaddonapiagents/wow-api-important)
Your own site
<a href="https://agentmods.dev/instructions/jburlison/wowaddonapiagents/wow-api-important"><img src="https://agentmods.dev/badge/instructions/jburlison/wowaddonapiagents/wow-api-important/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.

agentmods 80×15 button for WoW client-aware API guidance

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jburlison/wowaddonapiagents/wow-api-important"><img src="https://agentmods.dev/badge/instructions/jburlison/wowaddonapiagents/wow-api-important.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 389 This file is loaded in full into every session.
When invoked 389 The same file — it is already loaded in full.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00389 $0.00389
Opus 5.5 $0.00156 $0.00156
Sonnet 5.5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

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

Security

Grade C, and why

WoW client-aware API guidance scanned grade C 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 5d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- Generated by npm run build from instructions/wow-api.instructions.md. -->
.github/instructions/wow-api-important.instructions.md · 18 lines

What it actually says

WoW target selection

Use wow-addon-development and wow-client-targets. Resolve explicit targets or inspect the addon's existing configuration; ask when ambiguous. Supported targets are Retail (live), Forever (forever), and Classic progression (classic). All means those three only.

Pin source evidence per target. Verify signatures, event payloads, loaded templates, and addon restrictions before use. Apply Secret Values, combat restrictions, and deprecations only where verified for that client/build. Historical Retail 12.0.0 notes are not universal rules. Use separate target artifacts with shared core code and verified adapters. Report offline/stale evidence and distinguish static checks from in-game validation.

For visible UI changes, follow the workflow's mock-up choice before implementation, honoring an existing answer or accepted design. Use UIForever testing for available matching flavors; simulator checks do not replace real-client tests.

Preserve the accepted design using the visual-fidelity checks. Do not silently replace custom artwork with stock skins; combine custom textures and native interaction when appropriate, then compare actual rendered screenshots. Use connected client testing for available Witchcraft context/error tools and native computer use, without assuming either is installed or that no errors proves visual accuracy.

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.

  1. 5d ago Changed · +2 lines · +103 tokens per session 678969d1461d
  2. 6d ago Changed · -415 lines · -4,383 tokens per session scan A → C c7803444ef27
  3. 2mo ago First seen · 431 lines · 4,669 tokens per session scan A c3c6b0fca2e4

Subscribe to this mod's changes

WoW client-aware API guidance is an instructions file published in the GitHub repository JBurlison/WoWAddonAPIAgents (71 stars, last pushed yesterday), licensed MIT. It adds 389 tokens to every session, about $0.0016 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

WoW client-aware API guidance compared with instructions from other repositories

WoW client-aware API guidance next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
WoW client-aware API guidanceJBurlison/WoWAddonAPIAgentsInstructions file71yesterdayMITC389GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode