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.
npx agentmods add skills/jburlison/wowaddonapiagents/agent-file-specsnpx skills add JBurlison/WoWAddonAPIAgents --skill agent-file-specsgit clone --depth 1 https://github.com/JBurlison/WoWAddonAPIAgentsWrote 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/jburlison/wowaddonapiagents/agent-file-specs)<a href="https://agentmods.dev/skills/jburlison/wowaddonapiagents/agent-file-specs"><img src="https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/agent-file-specs.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00088 | $0.01110 |
| Opus 5 | $0.00044 | $0.00555 |
| Sonnet 5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
agent-file-specs 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 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.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Assistant Customization File Specifications
This skill provides the authoritative, up-to-date specifications for all AI coding assistant customization file types. Each file type has its own dedicated reference document with complete attribute tables, validation rules, examples, and best practices.
Standard: These specs align with the Agent Skills open standard and the VS Code Copilot customization documentation.
How to Use This Skill
- Read the Quick Reference below to identify the file type you need.
- Follow the link to the dedicated reference document for full details.
- Use the File Locations reference when you need to know where files go for a specific provider.
- Use the Settings reference for VS Code configuration.
Important: Detailed specifications live in the
references/folder — not in this file. This keeps the main skill file lightweight for efficient context loading per the progressive disclosure model.
Quick Reference
| Type | Extension | Purpose | Reference |
|---|---|---|---|
| Agent | .agent.md / .md |
Custom AI personas with specialized behaviors, tool restrictions, and handoff workflows | AGENTS.md |
| Skill | SKILL.md (directory-based) |
Reusable, portable capabilities with scripts and resources — follows the Agent Skills open standard | SKILLS.md |
| Prompt | .prompt.md |
Reusable prompt templates invoked as slash commands | PROMPTS.md |
| Instruction | .instructions.md |
Contextual guidance applied automatically by file type or description | INSTRUCTIONS.md |
| File Locations | — | Provider folder mapping, directory structure, naming conventions | FILE-LOCATIONS.md |
| VS Code Settings | — | Settings that control customization file discovery and behavior | SETTINGS.md |
What ships with it
6 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.
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.
- 5d ago First seen · 98 lines · 88 tokens per session scan A 69eb4593d156
agent-file-specs is a skill published in the GitHub repository JBurlison/WoWAddonAPIAgents (43 stars, last pushed 6mo ago), licensed MIT. It adds 88 tokens to every session and 1,110 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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.
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…