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 skills add JBurlison/WoWAddonAPIAgents --skill generate-agent-docsgit 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/generate-agent-docs)<a href="https://agentmods.dev/skills/jburlison/wowaddonapiagents/generate-agent-docs"><img src="https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/generate-agent-docs/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/jburlison/wowaddonapiagents/generate-agent-docs"><img src="https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/generate-agent-docs.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00063 | $0.01332 |
| Opus 5.5 | $0.00025 | $0.00533 |
| Sonnet 5.5 | $0.00013 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
generate-agent-docs 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.
How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Agent Documentation
Creates user-friendly documentation for AI coding assistant customization files.
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
- Onboarding new team members to your agent ecosystem
- Creating a catalog of available agents and skills
- Generating usage examples for specific agents
- Documenting your customization setup for reference
Documentation Types
Individual Item Documentation
Generate detailed docs for a single agent, skill, prompt, or instruction.
Catalog Documentation
Generate a comprehensive overview of all customization files.
Output Templates
Agent Documentation
# Agent: [Agent Name]
## Overview
[What this agent does and why it exists]
## When to Use This Agent
Use `@[agent-name]` when:
- [Scenario 1]
- [Scenario 2]
- [Scenario 3]
**Don't use** when:
- [Anti-pattern 1]
- [Anti-pattern 2]
## How It Behaves
This agent will:
- [Behavior 1]
- [Behavior 2]
- [Behavior 3]
## Example Conversations
### Example 1: [Scenario Title]
**You:** [Example user message]
**Agent:** [How agent responds - summarized]
### Example 2: [Scenario Title]
**You:** [Example user message]
**Agent:** [How agent responds - summarized]
## Tips for Best Results
- [Tip 1 for effective usage]
- [Tip 2 for effective usage]
- [Common mistake to avoid]
## Related
- **[Related Agent]**: Use for [distinction]
- **[Related Skill]**: This agent uses this for [purpose]
Skill Documentation
# Skill: [Skill Name]
## Purpose
[What this skill accomplishes]
## Triggers
This skill activates when:
- [Trigger keyword/scenario 1]
- [Trigger keyword/scenario 2]
## What It Does
[Step-by-step of what the skill does]
## Used By
- [Agent 1] - for [purpose]
- [Agent 2] - for [purpose]
## Example
**Scenario:** [Description]
**Input:** [What's provided]
**Output:** [What's produced]
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 · 267 lines · 63 tokens per session scan A bac53e60adea
generate-agent-docs is a skill published in the GitHub repository JBurlison/WoWAddonAPIAgents (46 stars, last pushed 8mo ago), licensed MIT. It adds 63 tokens to every session and 1,332 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.
Other skills, from other repositories
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…
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…
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…
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…
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…