What is validate-agent-files?

A reference guide to World of Warcraft Retail APIs for mounts, pets, pet battles, toys, hunter stables, and heirlooms. These APIs let an addon read and manage a player’s collected game items and related systems.

Use it when working on addon features for browsing, filtering, favoriting, summoning, or managing mounts, pets, toys, stable pets, and heirlooms.

It puts the relevant collection API functions and their purposes in one place. This reduces the need to search through general game API documentation while building an addon.

validate-agent-files — Skill for Claude Code and Codex 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 validate-agent-files

Clone the repo

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

Made for: Claude Code, Codex.

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/validate-agent-files/github.svg)](https://agentmods.dev/skills/jburlison/wowaddonapiagents/validate-agent-files)

Your own site

<a href="https://agentmods.dev/skills/jburlison/wowaddonapiagents/validate-agent-files"><img src="https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/validate-agent-files/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/validate-agent-files"><img src="https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/validate-agent-files.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,489 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.00067	$0.01489
Opus 5.5	$0.00027	$0.00596
Sonnet 5.5	$0.00013	$0.00298
Haiku 4.5	$0.00007	$0.00149

Measured 1mo ago against content hash 25755c6abd59, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate-agent-files 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 1mo 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.

.github/skills/validate-agent-files/SKILL.md · 204 lines

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.

Validate Agent Files

Validates that agent, skill, prompt, and instruction files follow the correct format and structure.

Provider Folder Reference

This skill works across multiple AI coding assistant providers:

Provider	Base Folder
GitHub Copilot	`.github/`
Claude Code	`.claude/`
Codex	`.codex/`
OpenCode	`.config/opencode/`

Throughout this document, <provider>/ represents your chosen provider's base folder.

When to Use

Before committing new agents, skills, prompts, or instructions
When an agent isn't behaving as expected
To audit existing customization files for issues
After modifying any .github customization files

Validation Process

Step 1: Identify File Type

Determine the type based on location and extension:

<provider>/agents/*.md → Agent file (user-invokable)
<provider>/agents/*.subagent.agent.md → Sub-agent file (workflow component)
<provider>/skills/*/SKILL.md → Skill file
<provider>/prompts/*.prompt.md → Prompt file
<provider>/instructions/*.instructions.md → Instruction file

Step 2: Apply Type-Specific Validation

Agent File Validation (`<provider>/agents/*.md`)

Required Structure:

---
name: agent-name
description: When to use this agent (should include examples)
user-invokable: true  # Optional, defaults to true
---

[System prompt body]

Supported Frontmatter Attributes:

name (required) - Agent identifier
description (required) - When/how to use, with examples
user-invokable (optional) - Set to false for sub-agents (default: true)
tools - List of allowed tools
model - Specific model to use
handoffs - Other agents this can delegate to

Checks:

✓ YAML frontmatter present with --- delimiters
✓ name field exists and is non-empty
✓ description field exists (recommend 50+ characters with examples)
✓ Body content exists after frontmatter
✓ If tools specified, they are valid tool names
✓ If filename contains .subagent.agent.md, verify user-invokable: false is set

Read the full file on GitHub · 204 lines

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.

1mo ago First seen · 204 lines · 67 tokens per session scan A 25755c6abd59

Subscribe to this mod's changes

validate-agent-files is a skill published in the GitHub repository JBurlison/WoWAddonAPIAgents (46 stars, last pushed 8mo ago), licensed MIT. It adds 67 tokens to every session and 1,489 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-08-30.

Building agents

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens